Date: Fri, 29 Mar 2024 15:54:44 +0000 (UTC)
Message-ID: <1102481208.3787.1711727684939@aws-us-west-2-tungsten-confluence-1.web.codeaurora.org>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_3786_249721538.1711727684938"
------=_Part_3786_249721538.1711727684938
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Code Review platform
Code Review platform
How are existing reviews going to be handled?
How will cutover be handled?
- Pull requests (reviews in gerrit) are merge based. Scripting / to=
oling required to have the support for fast-forward merge requests for comm=
its.
- Gitflow provides better workflow management for the Git PR to the=
trunk and release branches
- Better UI and search capability
- Good collaboration with other community based open source softwar=
e
- Pull requests that are draft mode needs prefix "WIP" (Work in pro=
gress) and need tooling for filtering
- Predefined events for Webhooks
- Simple and easy to understand and onboard
- Checkpoint pull request. This enables to "checkpoint" tasks as th=
ey succeed in a way which allows to see results as the =
pipeline proceeds.
- Sometimes, a workflow policy might mandate a clean commit history witho=
ut merge commits. In such cases, the fast-forward merge is the perfect cand=
idate. With fast-forward merge requests, you can retain a linear Git histor=
y and a way to accept merge requests without creating merge commits.
- Atomic/related changes in all one commit is necessary for context affin=
ity, relativity and granularity to better manage the changes as a set funct=
ion.
- Submit the change set in the review as "draft" to provide better filter=
ing, visibility and manageability
- Pre-commit code review and comment on diffs
- Rating for the reviews which makes visibility better than looking for c=
omments, especially in an automated workflow
- Better diff ability on the rebase and squash for the review thread, esp=
ecially when a inline review comments were made to the original / subsequen=
t review submissions.
- Permission model by using tags on top of git set permission which provi=
des CI admins control over the reviews. This helps with consistency and ope=
rations, from CI to release.
- Better integration with issue tracking, workflow and automation via web=
hooks (jira, launchpad etc)
- Better integration with Jenkins
- Customizable webhooks using hooks plugins
- No intuitive UI
- Poor CLI consistency
------=_Part_3786_249721538.1711727684938--