-
Notifications
You must be signed in to change notification settings - Fork 102
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
Unable to Expand Org Team #55
Comments
Hmm that's really interesting. Can you use the GitHub CLI and make the following request?
Does that succeed, or do you get a 404 from that as well? |
Hey +1 !
I've changed to match my config and I have the same 404 that my Github action failed on. |
Hey , So I have cracked the issue its down to how Github handles certain characters in names When you have a team name containing "." these are replaced with "-" in the team name Slug
by updating the team name slug to show the following the issue is now resolved
|
Works perfect now just went through a test run 👍🏻 |
Wow that's really interesting, I didn't know that. I'm going to reopen this, I think this behavior isn't intuitive so this action should handle this without the user having to know this behavior. |
Currently if you have an org team name with a period in it, the team will not be found with a 404 response. This is because the GitHub API requires that the periods are replaced with hyphens. This PR fixes this behavior and closes #55. Signed-off-by: Thomas Stringer <thomas@trstringer.com>
Hi There
Currently utilising this action within a new pipeline and have ran into the following issue.
This works when using individual org users but not team names.
Any help appreciated!
The text was updated successfully, but these errors were encountered: