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

Config generated during build is put in current working directory #97

Closed
basilfx opened this issue Dec 1, 2020 · 2 comments · Fixed by #115
Closed

Config generated during build is put in current working directory #97

basilfx opened this issue Dec 1, 2020 · 2 comments · Fixed by #115
Labels
bug Something isn't working released

Comments

@basilfx
Copy link

basilfx commented Dec 1, 2020

I have a solution in a root folder, with an operator project in src/operator-project/.

If I run dotnet build on a solution in the root folder, then the config folder is generated in config/. If I run dotnet build in src/operator-project/, then the config folder is generated in src/operator-project/config.

Given that generated config files are generated at build-time, and belong to the src/operator-project/, I would not expect them in the root folder (or actually, the current working directory), no matter how you compile it.

@buehler buehler added the bug Something isn't working label Dec 5, 2020
@buehler
Copy link
Owner

buehler commented Dec 5, 2020

mhmm this is a good point.

@github-actions
Copy link

🎉 This issue has been resolved in version 2.5.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working released
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants