Skip to content

feat(get-workflow-token): Add condition to check the GitHub repository owner#99

Merged
chazypro merged 2 commits intomainfrom
feat-get-token-restrict
Aug 28, 2024
Merged

feat(get-workflow-token): Add condition to check the GitHub repository owner#99
chazypro merged 2 commits intomainfrom
feat-get-token-restrict

Conversation

@chris3ware
Copy link
Copy Markdown
Member

This workflow should not be called from outside of the 3ware organisation because it creates an installation access token for the 3ware release GitHub App.

This has been tested from a user GitHub account and the action does fail, because the user account does not have access to secrets required for the action to run.

Adding the condition to check for the owner, skips the workflow entirely. This resolves #98

@chris3ware chris3ware requested a review from a team as a code owner August 28, 2024 11:08
To ensure that this workflow cannot be run outside the 3ware
GitHub organisation.
@chris3ware chris3ware force-pushed the feat-get-token-restrict branch from 0fa0c87 to 9418e51 Compare August 28, 2024 11:38
@chazypro chazypro merged commit 7450cd6 into main Aug 28, 2024
@chazypro chazypro deleted the feat-get-token-restrict branch August 28, 2024 12:13
3ware-release Bot pushed a commit that referenced this pull request Aug 28, 2024
## [3.1.0](v3.0.1...v3.1.0) (2024-08-28)

### Features

* **get-workflow-token:** Add condition to check the GitHub repository owner ([#99](#99)) ([7450cd6](7450cd6))
@3ware-release
Copy link
Copy Markdown
Contributor

3ware-release Bot commented Aug 28, 2024

This PR is included in version 3.1.0

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

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Limit access to get-workflow-token workflow

2 participants