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

📖 Add clarity on automatic version bump in docs / PR checklist #11813

Merged
merged 1 commit into from
Apr 7, 2022

Conversation

Phlair
Copy link
Contributor

@Phlair Phlair commented Apr 7, 2022

What

Removed manual steps from PR checklist that are now automated (#11712)

@Phlair Phlair requested a review from edgao April 7, 2022 17:55
@Phlair Phlair self-assigned this Apr 7, 2022
@github-actions github-actions bot added the area/documentation Improvements or additions to documentation label Apr 7, 2022
Copy link
Contributor

@edgao edgao left a comment

Choose a reason for hiding this comment

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

one question but lgtm otherwise

@@ -124,8 +124,8 @@ Once you've finished iterating on the changes to a connector as specified in its
/publish connector=(connectors|bases)/<connector_name>
```

4. OPTIONAL: Only necessary if the automated connector version bump fails
* Update the connector definition in the Airbyte connector index to use the new version:
4. OPTIONAL: Necessary if this is a new connector, or the automated connector version bump fails
Copy link
Contributor

Choose a reason for hiding this comment

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

if the bump fails, that fails the entire /publish command right? I.e. you'd have to rerun /publish, at which point it would try to bump again?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I kept the flow the same order as before, so first it publishes the connector and if that succeeds, it then does the auto version bump.

That means it can successfully publish but then fail auto-bump, this shouldn't happen so if it does, manual eyes figuring out why is a good thing. This should be clear based on the comments that get added back to the git comment.

Copy link
Contributor

Choose a reason for hiding this comment

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

ah nice, makes sense 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants