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

Update the sample in README.md with explicit permission control. #31

Merged
merged 2 commits into from
Sep 26, 2024
Merged

Update the sample in README.md with explicit permission control. #31

merged 2 commits into from
Sep 26, 2024

Conversation

suikan4github
Copy link
Contributor

By adding the explicit permission declaration, the user can deploy the HTML document with the default workflow permission of their repository.

    permissions:
      contents: write
      pages: write

In issue #24, It is suggested to change the Workflow permission of the user repository setting from "Read repository contents and packages permissions" (default) to "Read and write permissions", to avoid the error at deployment by GitHub actions (See the figure below).

2024-09-25 (2)

This explicit permission declaration in this pull request has two advantages compared to the one suggested in Issue #24.

  1. The user of doxygen-github-pages-action doesn't need to change the repository workflow permission from the default ( easy to use ).
  2. The user can keep the repository workflow permission in a strict state ( global safe ).

The changed YAMLs inside README.md have been tested with my test repository. I confirmed they work fine.

By adding the explict permission declaration, user can deploy the
HTML document with default workflow permission of their repository.

    permissions:
      contents: write
      pages: write
README.md Outdated Show resolved Hide resolved
@DenverCoder1
Copy link
Owner

Looks great! Thanks for the contribution 🎉

@DenverCoder1 DenverCoder1 merged commit a5ce84b into DenverCoder1:main Sep 26, 2024
@suikan4github
Copy link
Contributor Author

My pleasure. Thank you for merging the PR. Have a good day!

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.

2 participants