New feature in same plugin we did code in house and want to share#5
New feature in same plugin we did code in house and want to share#5Quardah wants to merge 9 commits intoBoTreeConsultingTeam:masterfrom
Conversation
ParthBarot-BoTreeConsulting
left a comment
There was a problem hiding this comment.
Hi @Quardah ,
Thanks for taking time to submit this PR, really appreciate! The code looks good, and a nice idea to update the ticket state automatically! 👍
I have just one suggestion so that we can keep current and next status code as configurable, without requiring any code changes!
Thanks,
Parth
|
Hi. I just did the push. Thank you for your time. |
… missing env var (no default), updated readme
|
Hi, me again, i have updated the code again. 1 - fixed lables order (no_pr_found and no_update were inverted in the code) Thank you for your feedback i hope you appreciate this contribution. |
Hi BoTreeConsultingTeam i hope you are doing well.
Starting from your work we developed a new feature to add in this plugin. Maybe some other user will see this plugin and eventually want to use the feature.
It's pretty bare-bone, but this feature allows for tickets to be automatically updated when receiving a PR webhook from github.
You can setup the same webhook as you did but change the payload URL to "github_change_notification" instead of "create_comment". It uses the same github_secret_token, so on github paste the same token. It also uses the same
- #rmXXXscheme you are using for commits message, but it must be included in the PR title.To use the feature now, setup the following two environment variables :
CURRENT_REDMINE_STATE
NEXT_REDMINE_STATE
Before starting Redmine (the same as setting up the Github Token variable). To get the status numbers, in redmine administration, hover over the status and the link target will contain the status number ID.
If none are set, the default CURRENT will be 2 (In Progress) and the default NEXT will be 3 (In Review).
This work has been done during my employment at FJNR (Web site - Github) with the participation of Noel Rignon regarding the research and analysis of your plugin, with the goal of having automations on our internal task management processes.