Reflecting in last weekends experiment in HS I feel more and more that mapping jobs to github milestones is the wrong idea:
1. I can't seem to find a way to even point to a milestone page in github!! Pointing to issues works as expected but ... milestones seem to not be a top level object in github's model
2. I can't seem to create a hook against a milestone status change (so as I can automate for example my OD job completion
3. The milestone description editor isn't as good as the issue description editor.
4. It is really non-obvious to navigate to a milestone - it is more of a grouping tag than a standalone object
On the other hand mapping issues to jobs has its own weaknesses.
1. When the user submits a pull request ... it becomes yet another issue
2. No obvious way to relate the two issues together.
The last thing seems a rather obvious weakness. I wonder why isn't that part of the typical use case of a person that runs his project from github. They capture various bugs they find, enhancements they plan to do as issues. The issue list also grows as people report bugs make enhancement requests. Everytime an external contributor takes on an issue and fixes it, the pull request will create a new issue.. Quick look at various projects shows that people use naming conventions like "fixes Issue xxx".
Looking at stackoverflow for preferred workflow... doesn't bring an exact match to this problem...actually it does... Surprising.. so it is feasible to associate a pull request to an existing issue but thats available only at the api level!!... or with my favorite gihub command line utility.. hub.
$ hub pull-request -i 4
This means that eventually we can have our cake and eat it too. I think I am switching..
Next experiment will be using issues as OD jobs.
No comments:
Post a Comment