<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof ContentPasted0">
Hi George,<br>
<br>
First time using GitHub here and it looks like I need to re-sign the contributor license agreement. This is approved in Jira, how do we go about signing this in GitHub?<br>
<br>
I'm sure others will have the same issue so thought it was pertinent to reply to this thread.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof ContentPasted0">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);" class="elementToProof ContentPasted0">
Regards,<br>
<br>
Ross<br>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> asterisk-dev <asterisk-dev-bounces@lists.digium.com> on behalf of George Joseph <gjoseph@sangoma.com><br>
<b>Sent:</b> 06 June 2023 12:22<br>
<b>To:</b> Asterisk Developers Mailing List <asterisk-dev@lists.digium.com><br>
<b>Subject:</b> [asterisk-dev] GitHub: One Month Update</font>
<div> </div>
</div>
<div>
<div dir="ltr">It's been a month now since we transitioned over to GitHub so I thought I'd give you guys an update but I'd also like to hear your thoughts on the transition and new process.
<div><br>
</div>
<div>First...A Policy Change...</div>
<div>When we started, we said "one commit per pull request" to keep things as close to Gerrit as possible. After some discussions and additional thinking however, it looks like we can allow multiple commits per pull request under the following condition:
The commits MUST be for a single functional change and must be able to stand on their own, in sequence from first to last commit. For example, a commit that adds some core capability to JSON processing, then a second commit that updates an app or function
to use it. In this case, the first commit can stand on its own and the second depends on it so having both commits in the same PR would make sense. Another good example might be a large scale change required by a new gcc version where the files changed in
the apps directory might be in one commit and the files changed in funcs in another.</div>
<div><br>
</div>
<div>What's not acceptable are commits added to a PR that fix issues in other commits in the same PR. This would result in a commit that we know to be broken making it into the git history. An unknowing person might checkout that commit and not realize that
the following commit is also required. It would also make git-bisects troublesome. Also not acceptable are merge or other housekeeping commits. I've seen a few merge commits just in the past week. </div>
<div><br>
</div>
<div>Second...A Reminder...</div>
<div>Please keep an eye on your commit messages. Don't put anything extraneous after the Fixes/Resolves, UserNote or UpgradeNote trailers. Keep all legacy ASTERISK- mentions, Gerrit links, Reported-by and other stuff above all the new trailers. It would
also help me a great deal if you could update the pull request description to match the commit message if you happen to fix any of these issues after the PR is created. We don't parse the PR description at all but if I see issues in it I'll have to keep drilling
down to the commits to see if you've fixed them there.</div>
<div><br>
</div>
<div>Third...Merges...</div>
<div>We had some issues yesterday where two PRs were merged that both updated Alembic scripts. Each PR on its own passed all the tests and merge conflict detection but when actually merged broke the previous/next links between Alembic scripts. This happened
because we do most of the merge checks when PRs are submitted and none just before they're actually merged. GitHub isn't really set up to do pre-merge checks like Gerrit did and assumes that if a PR could be merged without git conflict, it must be good.
We're looking at ways to solve this issue which may include a new "Merge Queue" feature GitHub has in beta testing. It might take a few weeks to iron the kinks out though. In the mean time, we might automatically add an "ALEMBIC CHANGE!" flag to any PR that
touches the Alembic scripts just to make us aware that there might be a conflict.</div>
<div>
<div><br>
</div>
<div>Finally...Your Thoughts?</div>
<div>How's everything working from your perspective? Anything we should change?</div>
<div><br>
</div>
<span class="x_gmail_signature_prefix">-- </span><br>
<div dir="ltr" class="x_gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">
<div style="color:rgb(136,136,136); font-family:tahoma,sans-serif"><font color="#073763">George Joseph</font></div>
<div style="color:rgb(136,136,136); font-family:tahoma,sans-serif"><font color="#073763">Asterisk Software Developer</font></div>
<div style="color:rgb(136,136,136); font-family:tahoma,sans-serif"><font color="#073763">Sangoma Technologies</font></div>
<div style="color:rgb(136,136,136); font-family:tahoma,sans-serif"><font color="#073763">Check us out at <a href="http://www.sangoma.com/" target="_blank" style="color:rgb(17,85,204)">www.sangoma.com</a> and <a href="http://www.asterisk.org/" target="_blank" style="color:rgb(17,85,204)">www.asterisk.org</a></font></div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>