You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to get some metadata on the current news fragments, specifically the type. The idea is to save this result somewhere and use it to determine the semantic version to use. For instance, if the fragments were validated against my config and returned "bugfix,feat,bugfix,doc" I would use that and say, ok "feat" is the highest so I can run hatch version minor in my pipeline. Is this a good idea? bad idea?
As far as I can tell the closest way to do this is parse the towncrier check output. But that's not ideal because I can't take advantage of all of the useful utility functions already in place like parse_newfragment_basename. Is there an existing practical solution I am missing?
The text was updated successfully, but these errors were encountered:
Towncrier is not really designed to be integrated with other tools ... like hatch.
Also... there is no public Python API.
I think that if you need to implement a smart tool for hatch is better to create a custom plugin for hatching
I think that it's best to implement a tool outside of towncrier ... for example, before calling Towncrier, just check the content of your newsfragemnt directory and decide how to call the hatch command
I want to get some metadata on the current news fragments, specifically the type. The idea is to save this result somewhere and use it to determine the semantic version to use. For instance, if the fragments were validated against my config and returned "bugfix,feat,bugfix,doc" I would use that and say, ok "feat" is the highest so I can run
hatch version minor
in my pipeline. Is this a good idea? bad idea?As far as I can tell the closest way to do this is parse the
towncrier check
output. But that's not ideal because I can't take advantage of all of the useful utility functions already in place like parse_newfragment_basename. Is there an existing practical solution I am missing?The text was updated successfully, but these errors were encountered: