Skip to content

security(ci): disable persisted checkout credentials in read-only workflows #490

Closed

Description

@karagozemin

Why

Every workflow checkout currently leaves the GitHub token in the local Git credential configuration. These jobs only read and test code, so later build steps do not need reusable Git credentials.

Scope

Set checkout credential persistence off in all workflows.

Acceptance criteria

  • Add persist-credentials: false to every actions/checkout step.
  • Keep checkout depth and all existing job behavior unchanged.
  • Add a short comment explaining that downstream steps do not push.
  • Verify each workflow still reaches its first test or documentation check.

Do not add replacement tokens or credentials.

Activity

  1. added
    help wantedExtra attention is needed
    area: ciContinuous integration and developer tooling
    priority: highUrgent work with high project or security impact
    securitySecurity, supply-chain, and repository-hardening work
    on Oct 21, 2026
  2. emirykl commented on Oct 21, 2026

    @emirykl
    Contributor

    @emirykl has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hey, I want to take that issue

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @emirykl to this issue.

  3. abojeEdwin commented on Oct 21, 2026

    @abojeEdwin
    Contributor

    @abojeEdwin has applied to work on this issue as part of the Stellar Wave Program's 10th wave.

    Hello Maintainer, I've got a good understanding of this issue. I'm confident I can implement a fix fast. Kindly assign to me. Thank you

    ℹ️ Repo Maintainers: To accept this application, review their application or assign @abojeEdwin to this issue.

  4. drips-wave commented on Oct 21, 2026

    @drips-wave

    Congratulations, @abojeEdwin! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on October 22, 2026.

    🧑‍💻 @abojeEdwin: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

    Warning

    When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

    🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

    🌊 Happy Wave 🌊

  5. added 2 commits that reference this issue on Oct 23, 2026
    b57a06d
    738da53
  6. grantfox-oss commented on Oct 27, 2026

    @grantfox-oss

    🎉 This issue has been marked as completed on GrantFox!

    @abojeEdwin's PR #497 was approved and merged by @karagozemin.

    🏆 @abojeEdwin: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (573 total points). Track your full progress on GrantFox.

    👏 Great work, @abojeEdwin! Keep contributing to Sub-Rosa-Issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Stellar WaveIssue proposed for the Drips Stellar Wave programarea: ciContinuous integration and developer toolinggood first issueGood for newcomershelp wantedExtra attention is neededpriority: highUrgent work with high project or security impactsecuritySecurity, supply-chain, and repository-hardening work

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions