|
Notes |
|
|
|
|
Repository SHA -> Repository Link |
|
|
|
|
I think that probably a reasonable approach is:
- Each project can be linked one or more git repos (I love BitBucket and also use Github)
- Link to github repo from the project dashboard
- new issues in the repo create a new ticket in wbTeamPro (not vice-versa)
- integrate the git repo issues with the project issues/tickets ... updates in wbTeamPro sync to the repo and vice-versa.
- link tasks &/or milestones to issues. When task status is updated, so is the issue in Git.
- maybe/V2 > extra project view tab (admin & client side options) to display repo history (commits) & wiki. |
|
|
|
|
Please don't limit this just to github. There are lots of git solutions out there Plain git, Github, Bitbucket, Gitlab, AWS Codecommit.. instead of trying to build out integrations for each platform simplify it and just do webhooks. Allow a url to the wbteampro installation with a token. This token grants grants direct access to post in that project for that type of action.
https://example.com/modules/addons/wbteampro/api.php?jbjv20dv3f902gv8 [^]
is accessed on a push and updates the project with the various commits by the workers.
https://example.com/modules/addons/wbteampro/api.php?8vVJejc2lc8b3h31j [^]
is accessed on a new issue that is opened up and adds it to the wbteam tracker.
This would work with all the major git giants and take most of the work out of your hands since it would be simple reporting from a remote system. |
|
|
|
|
|
To add to my previous note, if you had a unique token per event per project in wbteampro then that would simplify things even more since all you'd need to do is make sure the incoming data is applied properly and then it would be done. |
|