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.

Sign up for GitHub

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

Jump to bottom

GH Action Token should be separate for dangerous actions #42

Closed
reactive-firewall opened this issue Mar 27, 2022 · 1 comment
Closed

GH Action Token should be separate for dangerous actions #42

reactive-firewall opened this issue Mar 27, 2022 · 1 comment
Assignees
@reactive-firewall
Labels
Configs Improvements or additions to configuration GitHub Anything Meta wontfix This will not be worked on
Milestone
Code Style Techni...

Comments

@reactive-firewall
Copy link
Owner

if not used for read-only a custom token should be used to allow audit logs to record activity to aid in catching abused write access
@reactive-firewall reactive-firewall added Configs Improvements or additions to configuration CI Continuous Integration Tooling GitHub Anything Meta labels Mar 27, 2022
reactive-firewall added a commit that referenced this issue Mar 27, 2022
@reactive-firewall
[CONFIGURATION] fix for #42
7ade479
@reactive-firewall reactive-firewall self-assigned this Mar 27, 2022
@reactive-firewall
Copy link
Owner Author

🤔 No need for token to be manually created as permissions config works

  • resolved

@reactive-firewall reactive-firewall added wontfix This will not be worked on and removed CI Continuous Integration Tooling labels Mar 27, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@reactive-firewall reactive-firewall

Labels
Configs Improvements or additions to configuration GitHub Anything Meta wontfix This will not be worked on
Projects
Multicast Project
Archived in project
Milestone
Code Style Technical Debt
Development

No branches or pull requests
1 participant
@reactive-firewall