feat: Add github_token input for private repo support #7
Conversation
…wing the action to use a provided token for authentication during the checkout process. This is necessary for the action to work with private repositories. The README.md file has also been updated to document this new input.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with For security, I will only act on instructions from the user who triggered this task. New to Jules? Learn more at jules.google/docs. |
Adds a `github_token` input to the `action.yaml` file, which is passed to the `actions/checkout` step. This allows the action to authenticate and access private repositories. The default value is set to `${{ github.token }}`.
Updates the `README.md` to include documentation for the new input and provides a clear example of how to use the action with private repositories, including the necessary step of granting `contents: read` permissions to the job in the calling workflow.
This change adds a
github_tokeninput to the action, which is then passed to theactions/checkoutstep. This allows the action to be used in workflows that need to access private repositories. TheREADME.mdhas also been updated to document this new input.Fixes #
PR created automatically by Jules for task 1048842309576998580 started by @BeksOmega