Skip to content
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.

Sign up for GitHub

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

Jump to bottom

fix: use custom config path to sanitize build names #280

Merged
merged 1 commit into from
Aug 29, 2021
Merged

fix: use custom config path to sanitize build names #280

merged 1 commit into from
Aug 29, 2021

Conversation

anbraten
Copy link
Member

@anbraten anbraten commented Aug 28, 2021 •
edited
Loading

closes #270

@anbraten
Copy link
Member Author

The docs should be updated to make clear how the name for depends_on in multi-pipelines is generated.

@6543 6543 added the bug Something isn't working label Aug 29, 2021
@6543 6543 added this to the 0.15.0 milestone Aug 29, 2021
@6543 6543 merged commit 8aeae0a into woodpecker-ci:master Aug 29, 2021
@anbraten anbraten deleted the fix-depends-on-custom-path branch August 29, 2021 20:28
@6543 6543 added the backport-done indicates that this pull has been backported label Sep 21, 2021
6543 pushed a commit that referenced this pull request Sep 21, 2021
@anbraten @6543
Use custom config path to sanitize build names (#280)
a0a58c5 
fix #270
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@6543 6543 6543 approved these changes

Assignees
No one assigned
Labels
backport-done indicates that this pull has been backported bug Something isn't working
Projects
None yet
Milestone
0.15.0
Development

Successfully merging this pull request may close these issues.

Bug: multi-pipeline depends_on not working with custom config-path
2 participants
@anbraten @6543