Skip to content

Owner question: move the push token into the fork-push Environment so the fork follows upstream again? #36

Closed

Description

@scuttletoby

Recommendation: yes, move the push token into the fork-push Environment now (2 commands, about 2 minutes).

Why: the fork's automatic jobs that push (following upstream T3 nightly, and the new CI release job in #35) refuse to run while FORK_PUSH_TOKEN is a repository secret, because any workflow file on any pushed branch could read a repository secret. An Environment secret is handed only to jobs on main. Until this is done, the fork does not follow upstream on its own and CI releases have to be made by hand.

Already done: the Environment fork-push exists, limited to the branch main.

What you do (anywhere you are logged in to gh as the repo owner):

gh secret set FORK_PUSH_TOKEN -R scuttletoby/t3code --env fork-push
gh secret delete FORK_PUSH_TOKEN -R scuttletoby/t3code

The first command asks you to paste the token. If you no longer have it, make a new fine-grained token: repository scuttletoby/t3code only, permissions Contents and Workflows read and write, then paste that.

Answer here with "done" (or "no" and why). Nothing else waits on you for this.

Activity

  1. scuttletoby commented on Nov 14, 2026

    @scuttletoby
    OwnerAuthor

    Owner decision 2026-11-14: yes. The owner is making a new fine-grained token and putting it in the fork-push Environment. Close when the secret is in the Environment and the repository secret is gone.

  2. scuttletoby commented on Nov 14, 2026

    @scuttletoby
    OwnerAuthor

    Done, thanks. FORK_PUSH_TOKEN is now only in the fork-push Environment and the repository secret is gone. The first follow run then failed to start for a separate reason (a permission mismatch between two workflow files, not the token): fix in #66. Once #66 merges I start the follow run by hand again.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions