-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
introduce a github action for open source release #5732
Conversation
# Conflicts: # .bumpversion.cfg
TODO(Subodh) : Need to add |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good overall. Just minor comments.
run: | | ||
echo "Pull Request Number - ${{ steps.cpr.outputs.pull-request-number }}" | ||
echo "Pull Request URL - ${{ steps.cpr.outputs.pull-request-url }}" | ||
- name: Next Steps |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we put these steps in the PR body instead of the Github Action? I don't think anyone will look at this usually.
@@ -44,15 +36,3 @@ SUB_BUILD=PLATFORM ./gradlew publish | |||
VERSION=$NEW_VERSION GIT_REVISION=$GIT_REVISION docker-compose -f docker-compose.build.yaml build | |||
VERSION=$NEW_VERSION GIT_REVISION=$GIT_REVISION docker-compose -f docker-compose.build.yaml push | |||
echo "Completed building and publishing..." | |||
|
|||
echo | |||
echo "Changelog:" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not blocking but nice to have:
It'd be cool if the changelog could also be put in the PR. I imagine you'd have to compute the changelog, save it to an output variable and then read it in the PR creation step?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is done directly in the pr_body.sh
now.
- name: Next Steps | ||
run: | | ||
echo "Steps After Merging PR" | ||
echo "1. Switch to master" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
echo "1. Switch to master" | |
echo "1. Pull most recent version of master" |
@jrhizor I addressed your comments, take a look at this PR https://github.com/airbytehq/github-workflow-test-repo-base/pull/30 , this is how the output PR would look from this new workflow. Let me know if you have any more feedback |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
- name: PR Details | ||
run: | | ||
echo "Pull Request Number - ${{ steps.cpr.outputs.pull-request-number }}" | ||
echo "Pull Request URL - ${{ steps.cpr.outputs.pull-request-url }}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: newline
tools/bin/pr_body.sh
Outdated
echo "Steps After Merging PR:" | ||
echo "1. Pull most recent version of master" | ||
echo "2. Run ./tools/bin/tag_version.sh" | ||
echo "3. Create a GitHub release with the changelog" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: newline
env: | ||
PREV_VERSION: ${{ steps.old_version.outputs.OLD_VERSION }} | ||
run: | | ||
chmod +x tools/bin/pr_body.sh |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we can chmod
the pr_body.sh
script and check that in so we don't have to do this in the workflow everytime.
@@ -1,6 +1,6 @@ | |||
[bumpversion] | |||
current_version = 0.29.13-alpha | |||
commit = True | |||
commit = False |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to make sure I understand, this is false because we are manually creating the commit later on in the workflow yes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@davinchia yup..now we dont want bumpversion
to commit changes. It would be taken care by the workflow
Wow, this is fancy! |
Issue : #5459
Action to create a PR : https://github.com/marketplace/actions/create-pull-request
Pre-merge Checklist
Expand the relevant checklist and delete the others.
New Connector
Community member or Airbyter
airbyte_secret
./gradlew :airbyte-integrations:connectors:<name>:integrationTest
.README.md
docs/SUMMARY.md
docs/integrations/<source or destination>/<name>.md
including changelog. See changelog exampledocs/integrations/README.md
airbyte-integrations/builds.md
Airbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
/test connector=connectors/<name>
command is passing./publish
command described hereUpdating a connector
Community member or Airbyter
airbyte_secret
./gradlew :airbyte-integrations:connectors:<name>:integrationTest
.README.md
docs/integrations/<source or destination>/<name>.md
including changelog. See changelog exampleAirbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
/test connector=connectors/<name>
command is passing./publish
command described hereConnector Generator
-scaffold
in their name) have been updated with the latest scaffold by running./gradlew :airbyte-integrations:connector-templates:generator:testScaffoldTemplates
then checking in your changes