-
-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid PR branch when used in repos with a leading dot #32
Comments
Hey, thanks for creating the Issue! This is definitely a problem which needs to be fixed.
That seems to be the easiest solution and might be useful for other requirements as well. I will add an option to specify a custom branch prefix instead of the I will start working on this tomorrow. |
I implemented this on the develop branch. You can try it out by using the action like this: uses: BetaHuhn/repo-file-sync-action@develop
with:
GH_PAT: ${{ secrets.GH_PAT }}
BRANCH_PREFIX: custom-branch I also added an example to the README which shows how you can use the @jezdez Let me know if this resolves your issue and I will merge this into master and release a new version. |
Friendly ping @jezdez |
Woops, sorry forgot to submit the form! Yep that did the trick, thank you :) |
No problem! 😄 |
🎉 This issue is resolved in version v1.6.0 🎉 To use the latest version, use the Action with the uses: BetaHuhn/repo-file-sync-action@v1 Or the uses: BetaHuhn/repo-file-sync-action@latest |
🐞 Describe the bug
When trying to use the action from a repo whose name starts with a dot like
.github
(community health files), it fails with git errors when it tries to create the PR branch:📚 To Reproduce
Use the action in a repo whose name wouldn't be a valid Git branch.
💡 Expected behavior
Invalid characters in names should be filtered out.
🖼️ Screenshots
If applicable, add screenshots to help explain your problem.
⚙️ Environment
📋 Additional context
Alternatively it would be great to be able to specify the name of the branch, or the branch suffix.
The text was updated successfully, but these errors were encountered: