You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And discovered that the Action is adding the newly created PR correctly to the Repo's Project named "Backlog" and column named "In progress".
...but is unexpectedly also adding the PR to an Owner project named "Global Backlog" and column named "In progress".
Reading the code, it seems like the Project Name is only fuzzily matched when searching for matching Columns through the Github API. The Project Name is not subsequently use it as a filter on the result for an exact match. Columns are filtered with an exact match.
Is the fuzzy-matching expected behavior?
I think this could also be addressed by #18 to avoid collisions (either fuzzily or exact match)
The text was updated successfully, but these errors were encountered:
Ahhh good catch. This should not be fuzzy matching.
I still want to keep the ability to add projects by name to keep this action usable for people who don't know how to get the project ID but it should only be getting exact matches.
If you want to make a pull request that would be awesome, otherwise I will fix this up in the next week or two.
I really love this Github Action, but ran into an unexpected situation:
I have the following action defined:
And discovered that the Action is adding the newly created PR correctly to the Repo's Project named "Backlog" and column named "In progress".
...but is unexpectedly also adding the PR to an Owner project named "Global Backlog" and column named "In progress".
Reading the code, it seems like the Project Name is only fuzzily matched when searching for matching Columns through the Github API. The Project Name is not subsequently use it as a filter on the result for an exact match. Columns are filtered with an exact match.
Is the fuzzy-matching expected behavior?
I think this could also be addressed by #18 to avoid collisions (either fuzzily or exact match)
The text was updated successfully, but these errors were encountered: