Skip to content

Conversation

CannonLock
Copy link

Updates the actions/checkout doc section to demonstrate how to push a commit using the generated token.

My experience was that I came here because I needed to push with a app token so my CI would run after.

So an example of how to do that would have been more helpful then a example on how to prevent using this token to push.

Closing my other PR as I think this better addresses what I came to the docs looking for.

Updates the `actions/checkout` doc section to demonstrate how to push a commit using the generated token. My experience was that I came here because I needed to push with a app token so my CI would run after. So an example of how to do that would have been more helpful then a example on how to prevent using this token to push. Closing my other PR as I think this better addresses what I came to the docs looking for.
@CannonLock CannonLock requested a review from a team as a code owner September 18, 2025 21:18
@Copilot Copilot AI review requested due to automatic review settings September 18, 2025 21:18
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

Updates the actions/checkout documentation to demonstrate pushing commits using the generated app token, replacing the previous example that showed how to prevent token persistence and use with prettier_action.

  • Replaces the persist-credentials: false configuration and prettier_action usage with a direct git push example
  • Adds steps showing file modification and committing changes using the app token
  • Provides a more practical workflow example for users who need to push commits that trigger CI

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
1 participant