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

Disable version-branching; add Ruff checks #18

Merged
merged 2 commits into from
Oct 8, 2024

Conversation

ryanjjung
Copy link
Collaborator

@ryanjjung ryanjjung commented Oct 3, 2024

Description of the Change

Two main changes here:

  • Remove the step of our workflow where merging a PR results in a vX.Y.Z branch being created. This cannot be done with GHA right now because our branch is protected.
  • Add a ruff check to the ruff format --check we were previously running. This catches more than just textual issues.

Benefits

We'll have some kind of automation and robotic double-checking, even if I have to cut version branches by hand for now.

Applicable Issues

Issue #17

@ryanjjung ryanjjung self-assigned this Oct 3, 2024
@ryanjjung ryanjjung added enhancement New feature or request ci labels Oct 3, 2024
@ryanjjung ryanjjung changed the title Fix workflow step for creating version branches Disable version-branching; add Ruff checks Oct 3, 2024
@ryanjjung ryanjjung requested review from malini and jdbass October 3, 2024 20:27
@ryanjjung ryanjjung mentioned this pull request Oct 3, 2024
#
# - When a PR is opened against `main`, or if that PR changes:
# - Figure out if any code changes have been made
# - Require a version number change
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure if we want this all the time; if we start a new project and want to stay in 'dev' mode on main until we release, then it would be meaningless to increment some artificial version number. IMO, if we want to make versioned releases, we should cut new branches with that intent.

Copy link
Collaborator

@malini malini Oct 4, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh, or is this just for this repo's workflow, and not part of the pulumi shared workflow code? Because then, that makes sense and you can disregard my comment.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This workflow is designed for this project's workflow only. This concerns how this project's PRs are processed.

@ryanjjung ryanjjung merged commit e978e03 into main Oct 8, 2024
12 checks passed
@ryanjjung ryanjjung deleted the fix-version-branch-step branch October 8, 2024 18:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants