ci: Automated merge-by comments and table

[traeok]

Proposed changes

Adds two new workflows to the .github folder of the repo:

• merge-by-comments.yml
  • posts merge-by dates when a new PR is opened (not in draft state) or marked as ready, as well as for existing PRs (before this workflow) once a new change is pushed
  • check the comment below by github-actions[bot] to see it in action 😋
• merge-by-table.yml
  • updates a PR Status List in the Discussions tab with PRs that have a merge-by date <= 1 week away
  • posts a reminder on open PRs with merge-by dates <24 hours away, tagging attached reviewers who haven't yet approved

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• Enhancement (non-breaking change which adds or improves functionality)
• Breaking change (a change that would cause existing functionality to not work as expected)
• Documentation (Markdown, README updates)
• Other (please specify above in "Proposed changes" section)

Checklist

General

• I have read the CONTRIBUTOR GUIDANCE wiki

[github-actions]

📅 Suggested merge-by date: 9/18/2024

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[JillieBeanSim]

Hey @traeok this is looking really cool. One question, why is the Update GitHub Project / Move project item (pull_request_target) check failing?

[traeok]

Hey @traeok this is looking really cool. One question, why is the Update GitHub Project / Move project item (pull_request_target) check failing?

Thanks Billie! This is because the token used for that action needs to have its permissions updated so it has write permission for pull requests. I was going to update it myself, but unfortunately the token permissions are restricted to a few users in the org and I do not have the necessary access to change them.

[zFernand0]

Hey @traeok this is looking really cool. One question, why is the Update GitHub Project / Move project item (pull_request_target) check failing?

Thanks Billie! This is because the token used for that action needs to have its permissions updated so it has write permission for pull requests. I was going to update it myself, but unfortunately the token permissions are restricted to a few users in the org and I do not have the necessary access to change them.

I was looking into this from the CLI perspective, but decided to move the investigation/test to a fork:

• Attempt to fix workflow permissions to publish GH releases zowe-cli#2252

More details, the token used for this specific action is the Zowe-Robot-token, which was created using the classic token method instead of fine-grained PATs. With classic tokens, the level of permission might be a bit too broad so we may be forced to create more fine-grained PATs going forward 😢

[zFernand0]

Seem like to learned a lot of graphQL 😋
LGTM! 🥳

[JillieBeanSim]

If it's not working why did it get approved and merged? @traeok @zFernand0 @awharn
FYI @adam-wolfe

[awharn]

I can't speak for why it was merged, but that check is failing across the entire org right now because someone changed Zowe's default permissions for the GITHUB_TOKEN to be read only in the workflows. We are in the process of opening pull requests in all of our repos to update all the workflows. It should be unrelated to the changes made here. That workflow is what updates the PRs and Issues on the project board on our standups. @JillieBeanSim

[zFernand0]

The Update project / Move Project Item workflow is not something required before a PR can be merged.
if those fail, it just means that the Projects tab on GitHub may be a bit out of date. However, I think it's ok for now since we update the board on every standup anyways 😋

[JillieBeanSim]

I understand the possibility of glitches/failures on existing workflows but it's not good practice to introduce new items (code, workflows, etc.) into the code base if not working during the time of introduction.

[JillieBeanSim]

@traeok please port these changes to the next branch. Thanks

[zFernand0]

I understand the possibility of glitches/failures on existing workflows but it's not good practice to introduce new items (code, workflows, etc.) into the code base if not working during the time of introduction.

Hey @JillieBeanSim,
I understand the concern, however these workflows (Update/Move Project Item) were added a little while ago, and started failing (I believe on August 28th) due to some setting changing at a higher level than the Zowe GH Org itself 😢

I'm more than happy to provide more details on a quick call if needed. 😋