-
-
Notifications
You must be signed in to change notification settings - Fork 12
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
when repo name contains number or '.' root pipeline is always ignored #87
Comments
Hmm, can you upgrade that to v3.6.12 (latest) and let me know if you have the same issue? I'll dig into this a bit more later this morning. Side note, also: there's no need to list |
i just tested with version 3.6.12, the issue persists |
Okay, I'll dig into this later today. Thank you for testing with latest, there were minor changes to the auto-detect regex so I wanted to make sure we were debugging with that. |
Hi, any update on this? :) |
Oh my! I will take a look this afternoon, then, and try to reproduce. sorry I had a lot of stuff come up with work the past two weeks |
its alright... :) |
@Joshua-Igoni again, apologies for this thread :P trying to reproduce this over in these two repos ~ https://github.com/emmeowzing/test-repo could I ask, what's the list of commands look like in the |
I had two repos that i testing with this orb. one had a simple name "test-repo" the other had name like "test-repo-2.0"
I set up basically two pipelines in each of them, the pipelines where very identical... for the first repo execution was fine, but for the second one with the number and "." the root pipeline was always ignored.
example pipeline configs to reproduce as follows:
app.yml(root-config pipeline)
the second pipeline that is listening for changes in a different directory
test.yml
then the config for dynamic/continuation
config.yml
as explained earlier, this works fine for repos containing no number and '.' in their name, but ignores root config pipeline when the repo name has a number and/or . in the name
The text was updated successfully, but these errors were encountered: