Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test issue for verifying the subscribe-to-label action works #320

Closed
1 task
AetherUnbound opened this issue Oct 20, 2022 · 6 comments
Closed
1 task

Test issue for verifying the subscribe-to-label action works #320

AetherUnbound opened this issue Oct 20, 2022 · 6 comments
Labels
🖼️ aspect: design Concerns related to design 🛠 goal: fix Bug fix 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work

Comments

@AetherUnbound
Copy link
Collaborator

Description

Test issue to trigger subscribe-to-label action.

Reproduction

  1. See error.

Screenshots

Environment

  • Device:
  • OS:
  • Browser:
  • Version:
  • Other info:

Additional context

Resolution

  • 🙋 I would be interested in resolving this bug.
@AetherUnbound AetherUnbound added 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🛠 goal: fix Bug fix labels Oct 20, 2022
@AetherUnbound AetherUnbound added the 🖼️ aspect: design Concerns related to design label Oct 20, 2022
@github-actions
Copy link

Subscribe to Label Action

cc @WordPress/gutenberg-design, @WordPress/openverse

This issue or pull request has been labeled: "🖼️ aspect: design"

Thus the following users have been cc'd because of the following labels:

  • WordPress/gutenberg-design: 🖼️ aspect: design
  • WordPress/openverse: 🖼️ aspect: design

To subscribe or unsubscribe from this label, edit the .github/subscribe-to-label.json configuration file.

Learn more.

@AetherUnbound AetherUnbound changed the title Test issue please ignore Test issue for verifying the subscribe-to-label action works Oct 20, 2022
@AetherUnbound
Copy link
Collaborator Author

AetherUnbound commented Oct 20, 2022

Gah, unexpected hiccup - it looks like the github-actions bot account can't use the @ groups 😞 I can edit and update the comment and it'll work I bet, but we don't want to do that every time it's used. I wonder if this means that one of us has to use our account (or the bot) to post it (this is for the WordPress/openverse group):
image

@AetherUnbound
Copy link
Collaborator Author

We're currently using secrets.GITHUB_TOKEN, I think if we use secrets.ACCESS_TOKEN that will use the @openverse-bot account which should have the right permissions to mention people 😮 @dhruvkb what do you think?

repo-token: "${{ secrets.GITHUB_TOKEN }}"

@dhruvkb
Copy link
Member

dhruvkb commented Oct 20, 2022

Yeah @AetherUnbound, switching to ACCESS_TOKEN should fix it. @openverse-bot is a regular user so it can tag anyone.

@AetherUnbound AetherUnbound added 🖼️ aspect: design Concerns related to design and removed 🖼️ aspect: design Concerns related to design labels Oct 21, 2022
@openverse-bot
Copy link
Collaborator

Subscribe to Label Action

cc @WordPress/gutenberg-design, @WordPress/openverse

This issue or pull request has been labeled: "🖼️ aspect: design"

Thus the following users have been cc'd because of the following labels:

  • WordPress/gutenberg-design: 🖼️ aspect: design
  • WordPress/openverse: 🖼️ aspect: design

To subscribe or unsubscribe from this label, edit the .github/subscribe-to-label.json configuration file.

Learn more.

@AetherUnbound
Copy link
Collaborator Author

Yay, subscription works! 😄 Thanks all for the help, Gutenberg Design folks - this issue requires no action on your part.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🖼️ aspect: design Concerns related to design 🛠 goal: fix Bug fix 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work
Projects
None yet
Development

No branches or pull requests

3 participants