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.

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

Use context input as a prefix for the context from compose services #136

Merged
merged 2 commits into from
Oct 15, 2023

Conversation

whoan
Copy link
Owner

@whoan whoan commented Oct 15, 2023

Closes #133

Good catch @Clashsoft

Test: whoan/hello-world#12

Test 1: Fails (as expected) when I don't provide the context to be used when processing the compose file: https://github.com/whoan/hello-world/actions/runs/6523592786/job/17714377588

Test 2: It is solved when I use context which now means "context for compose file": https://github.com/whoan/hello-world/actions/runs/6523600020/job/17714393215

@whoan whoan merged commit 1f0152b into master Oct 15, 2023
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

When using <folder>/docker-compose.yaml, the context is not relative to <folder>
1 participant