Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@smcintyre-r7
Copy link
Contributor

Replaces #20904. It should run this time because the PR branch is coming from the same repo and not a fork. The intention is to add all opened and reopened PRs to the primary kanban board for tracking.

@smcintyre-r7
Copy link
Contributor Author

Automation worked this time showing everything is all set. The action would also allow us to add issues to the board as well but that might be too much noise. It could be beneficial to add this automation to our other repos like metasploit-payloads, mettle, rex-core, rex-arch, etc. That way when PRs are added they'd flow right into our workflow and thus reduce the chances that they'd go unnoticed.

name: Add pull request to the kanban board

on:
pull_request:
Copy link
Contributor

@adfoster-r7 adfoster-r7 Jan 26, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should be pull_request_target:

https://stackoverflow.com/questions/74957218/what-is-the-difference-between-pull-request-and-pull-request-target-event-in-git

I don't think this pipeline needs a custom secret added either if the above is followed; At least based on actions/add-to-project#163 and it being the same approach we use for our label's script

@smcintyre-r7 smcintyre-r7 force-pushed the smcintyre-r7/feat/act/add-to-project branch from ef94480 to 5ac9c8a Compare January 27, 2026 18:33
@adfoster-r7 adfoster-r7 added the rn-no-release-notes no release notes label Jan 27, 2026
@adfoster-r7 adfoster-r7 merged commit 136a159 into master Jan 27, 2026
115 of 123 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

rn-no-release-notes no release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants