PR checker and updater for Jira missing stuff #15188
Conversation
…ssing in the title or the description. It updates the title with the ticket number and adds a comment with the link redirecting to the Jira ticket.
|
Is the title of this PR going to be updated with Jira ticket as well? :) |
|
Hi @QilongTang, it's supposed to be like that, but I think we have to wait to finish the validations to see the result. 😅 |
UI Smoke TestsTest: success. 2 passed, 0 failed. |
|
@sm6srw remember the error that I had in my private repo? It seems to be the same, I solved doing this in GitHub Configurations. |
|
Yes, those are the permissions we currently have,. |
|
Can u re-run the job? Enabling the debug logging? |
When an action id triggered in the context of PR from a fork, the Regarding Node.js 16 deprecation, the action itself needs to be updated. @AlexisErazoGlobant Can we find alternative action in the marketplace? |
|
@avidit Let me check for it, previously I found another one, but it seems it's made for its own company and its own Jira links, we could check together if you guys want. |
|
The repository for this check was recently updated to node 20 but the change has not been released yet to the marketplace. So I think we can try this one out now and add a task to update it when the new release is available. |
Purpose
Sometimes authors forget to add the ticket number to the title or/and add a Jira link to the description. So I'm adding the GitHub Action to check if the Jira ticket number is missing in the title or in the description. This updates the title with the ticket number and adds a comment with the link redirecting to the Jira ticket.
Declarations
Check these if you believe they are true
*.resxfilesRelease Notes
GitHub Action to check if the Jira ticket number is missing in the title or in the description. This updates the title with the ticket number and adds a comment with the link redirecting to the Jira ticket.
Reviewers
@sm6srw
FYIs