Explain Actions secret naming rules

User intention

Add an Actions secret to my account.

The intention is included in the agent’s input prompt alongside environment details and task instructions.

What breaks, and what should happen

Play Both
BeforeThe defect at the parent commit
0:00.00 / 0:00.00Frame 0 · Inspect the open Add secret dialog.

Enter a secret name beginning with a digit and inspect the generic validation feedback after Confirm.

AfterThe same script once the merged fix is applied
0:00.00 / 0:00.00Frame 0 · Inspect the open Add secret dialog.

Enter the invalid secret name, confirm it, and inspect the contextual naming guidance at Name.

How is it judged?

01 · Given
Restore the data and starting state.
An authenticated person has opened User Settings > Actions > Secrets > Add secret on an Actions-enabled instance. The new secret form is ready for Name and Value input.

02 · When
Perform the interaction.
Enter 1DEPLOY_KEY as Name, enter a non-empty Value, and click Confirm.

03 · Judge
Rationale: The leading digit violates a rule a generic format error does not explain. Specific guidance lets the user correct the name without guessing, while preserving the secret value avoids unnecessary re-entry.
Require
Block the invalid name and visibly explain at Name or in its validation feedback that secret names must start with a letter or underscore. Retain entered values so 1DEPLOY_KEY can be corrected.
Allowed
  • A persistent input hint, accessible contextual help, or specific validation message is acceptable if the violated first-character rule is understandable.
  • Native browser validation is acceptable when accompanied by meaningful rule guidance; a particular custom validator or error string is not required.
  • Other valid naming restrictions may remain; the fix need not accept names starting with digits.

Who repaired it

More from Gitea

Self-hosted Git forge with issues, CI and packages

Synchronize a canceled workflow in the run list after the reference repair
Developer tools
Synchronize a canceled workflow in the run list
The retained list continues to display Waiting throughout the observation. A separate diagnostic manual reload then displays Canceled for the same run, confirming that the list was stale after cancellation. The final screenshot is after that diagnostic reload; the preceding video shows the defect. This evidence concerns cancellation, not successful runner execution.
#38329
Preserve selections when batch closing issues fails after the reference repair
Developer tools
Preserve selections when batch closing issues fails
The native request fails with HTTP 412. The interface shows no error message, reloads the list, clears both selections, and restores the filter toolbar. All three issues remain open (3 Open, 0 Closed). A browser-console error is not feedback visible to the person using the list.
#38593
Use local tabs in the branch selector after the reference repair
Developer tools
Use local tabs in the branch selector
The tab adopts link-like hover styling. Clicking keeps the same Code page, dropdown, active Branches tab, and main branch content; the retained Reproduction issue context additionally reports an added trailing # and focus on Filter branch. The unchanged active-tab content is normal; the misleading link semantics and empty-fragment navigation side effect are the defect. Browser chrome is not present in the replay video, so the URL observation relies on the retained Reproduction context, not visual confirmation in the video.
#39285