Skip to content

Conversation

mashhurs
Copy link
Collaborator

@mashhurs mashhurs commented Jan 8, 2025

Thanks for contributing to Logstash! If you haven't already signed our CLA, here's a handy link: https://www.elastic.co/contributor-agreement/

@mashhurs mashhurs requested a review from donoghuc January 8, 2025 02:13
@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

@mashhurs mashhurs merged commit 09641c8 into elastic:main Jan 8, 2025
2 checks passed
@mashhurs mashhurs deleted the rename-gh-secret branch January 8, 2025 17:23
organization: elastic
team: logstash
GITHUB_TOKEN: ${{ secrets.READ_ORG_SECRET_JSVD }}
GITHUB_TOKEN: ${{ secrets.READ_ORG_SECRET_MASHHURS }}
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
GITHUB_TOKEN: ${{ secrets.READ_ORG_SECRET_MASHHURS }}
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

I dont understand why we need to tie this to someone's personal token. Why cant we use the one provided by GHA? https://docs.github.com/en/[email protected]/actions/security-for-github-actions/security-guides/automatic-token-authentication#permissions-for-the-github_token

Copy link
Member

Choose a reason for hiding this comment

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

Another bump for "why dont we use an off the shelf solution" #203 (review)

Copy link
Member

Choose a reason for hiding this comment

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

Oh, i see the default one applies only to the repo, not the org.

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.

4 participants