Skip to content

Handle the case where committing in CI doesn't make sense #87

@Andy-Grigg

Description

@Andy-Grigg

The 'Generate Client Library' CI workflow expects to always commit the generated code, but there are situations where that doesn't make sense:

  • Dependabot PRs - These generally shouldn't be making any changes to the code
  • Running CI on main - We don't want to push directly to main

For the dependabot PRs, not bumping the version number in this case might be a good option, since then the happy case will be no changes to the code, and the commit won't happen.

For running CI on main, this might just be a check to not commit on main, or potentially if run on main to always create a separate branch and PR.

Metadata

Metadata

Assignees

No one assigned

    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