branch names with @ are not processed #150817
Replies: 10 comments 5 replies
-
| 🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as  2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the  Thank you for helping bring this Discussion to a resolution! 💬 | 
Beta Was this translation helpful? Give feedback.
-
| I haven't found a solution (yet). | 
Beta Was this translation helpful? Give feedback.
-
| 🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as  2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the  Thank you for helping bring this Discussion to a resolution! 💬 | 
Beta Was this translation helpful? Give feedback.
-
| You're running into a limitation of GitHub Actions syntax: the uses: keyword expects the reference (ref) to be formatted like this: But  You can use a Temporary Branch With Dash/Slash Format Then in your workflow:  | 
Beta Was this translation helpful? Give feedback.
-
| 
 | 
Beta Was this translation helpful? Give feedback.
-
| ❗ Branch Names with  | 
Beta Was this translation helpful? Give feedback.
-
| GitHub Actions does not support @ characters in branch names when used in the uses: field because the @ symbol is a reserved character used to separate the action path from the ref (branch, tag, or commit SHA). like /uses: org/repo/path/file.yaml@fix@main | 
Beta Was this translation helpful? Give feedback.
-
| its best to not use any special chracters for your branch names use like main, master, test, dev , etc | 
Beta Was this translation helpful? Give feedback.
-
| 🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as  2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the  Thank you for helping bring this Discussion to a resolution! 💬 | 
Beta Was this translation helpful? Give feedback.
-
| 🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as  2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the  Thank you for helping bring this Discussion to a resolution! 💬 | 
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
I know I can use an action like:
However, when the branch name has an @ the workflow fails (we use branch names such as fix@main) to signal where the fix is going to get merged (main in this example)
The error message I get is:
I then need to use the SHA number which when I'm working on updating/fixing
org/repo/path/file.yamlI need to change each SHA for each commit.Is there any workaround to make it easier to use these branches (besides the obvious solution of not using this branch naming scheme)?
Beta Was this translation helpful? Give feedback.
All reactions