starred/act

Fork 0

mirror of https://github.com/nektos/act.git synced 2026-04-26 01:15:51 +03:00

[GH-ISSUE #979] Issue: No newline after the `Provide value for '<secret>'` #575

New issue

Closed

opened 2026-03-01 21:44:40 +03:00 by kerem · 4 comments

kerem commented

2026-03-01 21:44:40 +03:00

Owner

Originally created by @stdedos on GitHub (Feb 4, 2022).
Original GitHub issue: https://github.com/nektos/act/issues/979

System information

Operating System: Ubuntu
Architecture:
Apple M1:
Docker version:
Docker image used in act:
act version:

Expected behaviour

There seems to be no newline after the Provide value for '<secret>' prompt

Actual behaviour

Workflow and/or repository

`act` output

Log

PASTE YOUR LOG HERE

Originally created by @stdedos on GitHub (Feb 4, 2022). Original GitHub issue: https://github.com/nektos/act/issues/979  ## System information  - Operating System: Ubuntu - Architecture: - Apple M1: - Docker version: - Docker image used in `act`: - `act` version: ## Expected behaviour There seems to be no newline after the `Provide value for '<secret>'` prompt  ## Actual behaviour  ## Workflow and/or repository  ## `act` output  <details> <summary>Log</summary> ```none PASTE YOUR LOG HERE ``` </details>

kerem

2026-03-01 21:44:40 +03:00

closed this issue
added the
kind/bug

meta/resolved
labels

kerem commented

2026-03-01 21:44:41 +03:00

Author

Owner

@stdedos commented on GitHub (Feb 24, 2022):

Closed as ??? 😕

@stdedos commented on GitHub (Feb 24, 2022): Closed as ??? 😕

kerem commented

2026-03-01 21:44:41 +03:00

Author

Owner

@catthehacker commented on GitHub (Feb 24, 2022):

I have no idea what is the issue here also incomplete template

@catthehacker commented on GitHub (Feb 24, 2022): I have no idea what is the issue here also incomplete template

kerem commented

2026-03-01 21:44:41 +03:00

Author

Owner

@stdedos commented on GitHub (Feb 25, 2022):

I have no idea what is the issue here ...

It's pretty obvious if you read the title:

No newline after the Provide value for '<secret>'

or the issue:

There seems to be no newline after the Provide value for '<secret>' prompt

or, visually:

$ act --detect-event -s secrat --reuse
Provide value for 'SECRAT': WARN[0001] Cannot parse container options: --user 1001  
[Action] 🧪  Matrix: map[a:b c:d]

I am not sure what remains to be explained

... also incomplete template

Apologies, but I do not have an Apple M1: chip to fill the template with 😕

Also, another bug: You capitalize a secret's name when you shouldn't (notice that I gave -s secrat, you typed SECRAT).
https://docs.github.com/en/actions/security-guides/encrypted-secrets#naming-your-secrets

@stdedos commented on GitHub (Feb 25, 2022): > I have no idea what is the issue here ... It's pretty obvious if you read the title: > No newline after the `Provide value for '<secret>'` or the issue: > There seems to be no newline after the `Provide value for '<secret>'` prompt or, visually: ```console $ act --detect-event -s secrat --reuse Provide value for 'SECRAT': WARN[0001] Cannot parse container options: --user 1001 [Action] 🧪 Matrix: map[a:b c:d] ``` I am not sure what remains to be explained --- > ... also incomplete template Apologies, but I do not have an `Apple M1:` chip to fill the template with 😕 Also, another bug: You capitalize a secret's name when you shouldn't (notice that I gave `-s secrat`, you typed `SECRAT`). https://docs.github.com/en/actions/security-guides/encrypted-secrets#naming-your-secrets

kerem commented

2026-03-01 21:44:41 +03:00

Author

Owner

@catthehacker commented on GitHub (Feb 25, 2022):

Also, another bug: You capitalize a secret's name when you shouldn't (notice that I gave -s secrat, you typed SECRAT).

Not a bug

Secret names are not case-sensitive.

From the documentation you linked. We convert all secrets to upper case so they don't collide. On GitHub it also allows only uppercase secrets.

@catthehacker commented on GitHub (Feb 25, 2022): > Also, another bug: You capitalize a secret's name when you shouldn't (notice that I gave `-s secrat`, you typed `SECRAT`). Not a bug > Secret names are not case-sensitive. From the documentation you linked. We convert all secrets to upper case so they don't collide. On GitHub it also allows only uppercase secrets.

kerem referenced this issue

2026-03-01 21:51:28 +03:00

[PR #575] [MERGED] Update Shell Tasks to match ScriptHandlerHelpers #1504

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/act#575

No description provided.

Rows
Columns

[GH-ISSUE #979] Issue: No newline after the Provide value for '<secret>' #575

System information

Expected behaviour

Actual behaviour

Workflow and/or repository

act output

[GH-ISSUE #979] Issue: No newline after the `Provide value for '<secret>'` #575

`act` output