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

🐛 Auto release github action failure due to missing permissions #506

Conversation

scottc943
Copy link
Contributor

@scottc943 scottc943 commented Jan 31, 2024

What does this PR do?

This PR provides a fix for the auto release GitHub action proposed in the PR #499 by replacing the GITHUB_TOKEN with the ADMIN_RIGHTS_TOKEN secret.

Why is this change important?

This change is essential as it provides a fix for the auto release GitHub action.

How to test this PR locally?

Place this file in the same location (.github/workflows/release.yml) then successfully merge a PR into the rolling branch. Once this is done you should see the action successfully runs and in a moment you will see the new tag and release. Please create a Personal Access Token or PAT and assign it these settings below. Not pictured is only setting the token to have control of the websurfx repo (or your fork).
image

Once you are done, please copy the token since you will not be able to see it again. Then you must add the PAT as a secret called ADMIN_RIGHTS_TOKEN. Please paste in the token you copied from above here. You may follow these steps https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions?tool=webui#creating-secrets-for-a-repository

Note: I used webui screenshots and notes to be more beginner-friendly, but you can do this in the CLI as well.

Author's checklist

N/A

Related issues

None

scottc943 and others added 30 commits January 27, 2024 22:58
…te-release-versions

ci: add release.yml to help automate release versions
…te-release-versions

ci: add release.yml to help automate release versions - edited file f…
…in a line which pointed at a different variable
…te-release-versions

ci: add release.yml to help automate release versions - I had a typo …
…te-release-versions

ci: add release.yml to help automate release versions - Fixing the re…
…te-release-versions

ci: add release.yml to help automate release versions. Lowercased V s…
…te-release-versions

ci: changing structure of release.yml to be easier to understand
…te-release-versions

ci: #minor changes made
…te-release-versions

ci: #minor changes made to make rolling and stable both release branches
…te-release-versions

ci: #minor changes to hopefully turn off pre-release
…ate-release-versions

ci: #minor change - trying to make pre-release suffic set to nothing
…ate-release-versions

ci: #minor change - removed older release action for a better up to d…
…ate-release-versions

ci: #minor change to fixed the pre-release issue
…ate-release-versions

ci: #minor change to fixed the pre-release issue again
…ate-release-versions

ci: #minor change to fixed the pre-release issue again2
@neon-mmd neon-mmd changed the title Feature/400 git hub actions automate release versions pr 🐛 Auto release GitHub action failure due to missing permissions Feb 2, 2024
@neon-mmd neon-mmd changed the title 🐛 Auto release GitHub action failure due to missing permissions 🐛 Auto release github action failure due to missing permissions Feb 2, 2024
Copy link
Owner

@neon-mmd neon-mmd left a comment

Choose a reason for hiding this comment

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

Thanks ❤️ for working on this PR. We really appreciate it 👍 Since everything looks good. Will merge this PR as soon as possible 🙂.

Copy link
Collaborator

@alamin655 alamin655 left a comment

Choose a reason for hiding this comment

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

Approved! Let's merge this in. 👍

@mergify mergify bot merged commit 280c7e2 into neon-mmd:rolling Feb 3, 2024
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants