* Email notification when one is mentioned or added as a reviewer * Color text in comment box * Click a failed job, run the job with the *updated* branch * Allow one to reorder commits (e.g., the fix up commits generated from applying comments) and mark commits that should be fixed up * Easily retarget a branch, e.g., from main to release (currently I have to checkout to local machine, do rebase, then push)
--Junchao Zhang On Thu, Jan 20, 2022 at 7:05 PM Barry Smith <bsm...@petsc.dev> wrote: > > I got asked to go over some of my Gitlab workflow uses next week with > some Gitlab developers; they do this to understand how Gitlab is used, how > it can be improved etc. > > If anyone has ideas on topics I should hit, let me know. I will hit them > on the brokenness of appropriate code-owners not being automatically added > to reviewers. And support for people outside of the Petsc group to set more > things when they make MRs. And being to easily add non-PETSc folks as > reviewers. > > Barry > >
