At this point, there are, as far as I'm concerned, 2 showstoppers with the suggested github workflow:
1- Submitting a pull request (the equivalent of uploading a patch to Bugzilla) doesn't update the bug status. 2- Merging a pull request (or whatever you call the equivalent of comitting a patch to the main hg repo) doesn't post to changelog.
I think I heard someone mention there might be a way to automate #2 (although it's not implemented yet, unless I missed something). However, I can't think of a way to get #1 without considerable manual effort. (Tracking the branch associated with the bug on the developer's own github repo, if that would notify of pull requests, would require knowing when that branch is created and what it's called, neither of which can be automated as far as I can tell.)
no subject
git checkout develop
git branch andnowforsomethingcompletelydifferent
git checkout andnowforsomethingcompletelydifferent
vi README
git commit -a
git push --all
git branch feature/obsolete-email-bug4448
git checkout feature/obsolete-email-bug4448
vi cgi-bin/LJ/Console/Command/MakeInvites.pm
git push --all
hub pull-request -b dreamwidth/dw-free:develop
At this point, there are, as far as I'm concerned, 2 showstoppers with the suggested github workflow:
1- Submitting a pull request (the equivalent of uploading a patch to Bugzilla) doesn't update the bug status.
2- Merging a pull request (or whatever you call the equivalent of comitting a patch to the main hg repo) doesn't post to changelog.
I think I heard someone mention there might be a way to automate #2 (although it's not implemented yet, unless I missed something). However, I can't think of a way to get #1 without considerable manual effort. (Tracking the branch associated with the bug on the developer's own github repo, if that would notify of pull requests, would require knowing when that branch is created and what it's called, neither of which can be automated as far as I can tell.)
Anyone has an idea?