Skip to content

Issues with new changelog action features #535

@RobPasMue

Description

@RobPasMue

As ref: ci: updating Ansys actions to v7 - changelog related by RobPasMue · Pull Request #1348 · ansys/pyansys-geometry (github.com)

  • Whenever the config types are not defined, they get committed by the action. We shouldn't be committing that part IMO. We should only use the default config and throw it away once the fragment gets generated.
  • If I have a local configuration BUT I am requesting to use the default config, we should inform the users what's going to happen.. (i.e. the default config gets ignored).
  • We might have to clarify what the default config does --> web based changelog, We might want to expose a way to use default config for repo based changelog via an argument.
  • The doc-deploy-changelog action has to be adapted as well to use the default config. Currently if you remove the config but you try to build the towncryer changelog, it will fail.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions