Skip to content

Add a roadmap auto commenter for use by all repositories#11

Open
Exairnous wants to merge 2 commits into
mainfrom
reusable-roadmap-auto-commenter
Open

Add a roadmap auto commenter for use by all repositories#11
Exairnous wants to merge 2 commits into
mainfrom
reusable-roadmap-auto-commenter

Conversation

@Exairnous
Copy link
Copy Markdown
Member

@Exairnous Exairnous commented May 4, 2026

What?

Adds a workflow that will leave a comment on newly opened issues and pull requests about the roadmap status (i.e. that it isn't on any roadmap yet) of that issue/pull request that can be called by any Hubs Foundation repository.

Why?

So that people will know what to expect and so that someone doesn't have to manually respond to new issues/pull requests with a stock reply. Also, it's added as a reusable workflow so that changes to the comments or behaviour only have to be made to this workflow, rather than the workflow in every repository.

Examples

Comment on a newly opened issue:
2026-05-04_01-55

Comment on a newly opened pull request:
2026-05-04_02-05

How to test

  1. Add this to to the default branch of one of your repositories (with the guard limiting it to only run on Hubs Foundation repositories removed).
  2. Add a caller workflow (based on: #12) to your repository (change the path to point to your version of the reusable workflow).
  3. Open an issue and a pull request (without a roadmap label).
  4. See that the issue and pull request each have a comment added to them indicating they're not on a roadmap yet.
  5. Open an issue and a pull request (with a roadmap label, e.g. Roadmap: Test).
  6. See that no comment is added to the issue or pull request.

Documentation of functionality

Currently, this is fully automatic with no configuration options and it is for the Hubs Foundation's use only (so not appropriate to put in the Hubs Docs). This helps to apply the roadmap policy. In light of all this, I don't think any additional documentation is needed at present.

Limitations

None known.

Alternative implementations considered

None.

Open questions

None.

Additional details or related context

This won't add a comment if it finds a roadmap label has been added to the issue/pull request during creation.

Roadmap policy PR: Hubs-Foundation/policies-procedures-guidelines-public#25

This workflow will need a caller workflow added to each repository.
Initial companion PR to call this workflow: #12

Note: this is only intended to help convey our use of roadmaps and the status of an issue/PR on them (by providing one way notifications). It is not intended for this to expand into any sort of customer service auto-responder that would reply to all comments or that could be interacted with by people.

What: adds a workflow that will leave a comment on newly opened issues and pull requests about the roadmap status (i.e. that it isn't on any roadmap yet) of that issue/pull request that can be called by any Hubs Foundation repository.

Why: so that people will know what to expect and so that someone doesn't have to manually respond to new issues/pull requests with a stock reply.  Also, it's added as a reusable workflow so that changes to the comments or behaviour only have to be made to this workflow, rather than the workflow in every repository.

Note: this won't add a comment if it finds a roadmap label has been added to the issue/pull request during creation.
@Exairnous Exairnous force-pushed the reusable-roadmap-auto-commenter branch from 6480128 to 2db8d78 Compare May 4, 2026 06:02
What: modifies the check for pull requests from the `pull_request` event to the `pull_request_target` event and adds a warning comment about it.

Why: the `pull_request_target` event bypasses the normal workflow approval rules of the repository and allows the auto commenter to work for pull requests made from external contributors/their forks; it is also safer because it will only run the workflow file from the Hubs Foundation, not the external contributor's pull request (which is why GitHub allows it to run automatically for everyone).
@hobbs-Hobbler
Copy link
Copy Markdown
Collaborator

hobbs-Hobbler commented May 5, 2026

LGTM!

Special thanks for the screen captures for "issue" and "pull request"-- very helpful to see! 👀

Copy link
Copy Markdown
Member

@DougReeder DougReeder left a comment

Choose a reason for hiding this comment

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

works for me

@Exairnous
Copy link
Copy Markdown
Member Author

I've added a clarification about the motivation of the roadmap auto commenter to the Additional details or related context section of the PR description as requested at the May 6 documentation session.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants