Skip to content

Commit

Permalink
Use short SHA in multitenant PR names (#529)
Browse files Browse the repository at this point in the history
<!-- The PR description should answer 2 (maybe 3) important questions:
-->

### What

Small quality of life change.

<!-- What is this PR trying to accomplish (and why, if it's not
obvious)? -->

<!-- Consider: do we need to add a changelog entry? -->

### How

<!-- How is it trying to accomplish it (what are the implementation
steps)? -->
  • Loading branch information
danieljharvey authored Jul 10, 2024
1 parent 2e9b0ee commit b6ede41
Showing 1 changed file with 5 additions and 2 deletions.
7 changes: 5 additions & 2 deletions .github/workflows/update-multitenant-dep.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -35,6 +35,9 @@ jobs:
# get newest commit to use
LATEST_SHA="$(cd ndc-postgres && git rev-parse HEAD)"
# get short sha too for title
LATEST_SHORT_SHA="$(cd ndc-postgres && git rev-parse --short HEAD)"
BRANCH_NAME="update-ndc-postgres-to-$LATEST_SHA"
DEP_FILEPATH="Cargo.toml"
Expand Down Expand Up @@ -65,10 +68,10 @@ jobs:
# create a pull-requests containing the updates.
gh pr create \
--body "Commit in ndc-postgres: https://github.com/hasura/ndc-postgres/commit/$LATEST_SHA" \
--title "dep update: update ndc-postgres to $LATEST_SHA" \
--title "dep update: update ndc-postgres to $LATEST_SHORT_SHA" \
--head "$BRANCH_NAME" \
--base "main" \
--reviewer "hasura/native-databases"
--reviewer "hasura/api-pg"
# scream into Slack if something goes wrong
- name: Report Status
Expand Down

0 comments on commit b6ede41

Please sign in to comment.