-
Notifications
You must be signed in to change notification settings - Fork 107
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
Add support for calling towncrier from sub-directories not only from the repo root. #433
Comments
Hi, Thanks for the report. Can you share the content of the towncrier configuration file. Also, can you confirm the working directory from which you call the Regards |
I've tried calling it from and from |
Thanks for the confirmation... it looks like a bug But ... I don't think that we have documentation confirming that But it might be just missing documentation and this workaround is good enough. Try something like this in the root of the repo, with towncrier in the root of the repo
You can have separate multiple towncrier config files in root. |
@adiroiban that worked thanks 👍 so if I have many sub projects in a repo I have to call towncrier differently with each toml in the main root. e.g. if there is
Is it planned to add the feature for subprojects in the future? |
I would be happy to review a patch I don't know anyone planning to work on such a feature. towncrier is an open source project and anyone can send bugfixes or new features. |
I have updated the title of the issue to better describe what is missing . Since this is not a documented feature, we can't really call it a bug. It's just a missing feature. |
I have a repo that looks like this
where I want to use towncrier only in the sub_project directory (changes is where the fragments are). I've been able to create the first fragment in the default branch but when adding a new fragment
1234.feature
from a new branch and using thecheck
command liketowncrier check --compare-with origin/main
this is what produces
It has found the new fragment but doesn't recognize it as a new fragment. Also the directory that has checked
is
sub_project/sub_project
, which it doesn't exist.The text was updated successfully, but these errors were encountered: