ci: release candidate pull request doesn't have a reference to main branch

Open Beginner friendly
#593 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions, go
Domain
ci-cd, release

Research direction

Start at .github/workflows/release.yml around line 117 and inspect the release candidate pull request referenced in the issue, PR 579. Check how the workflow identifies the branch and how the release candidate is expected to reference main; done means the generated pull request includes that reference while the unit and E2E test checks remain passing.

Written by the indexing model from the issue text.

Description

bug build release

🔭 Odd happeneings found in release testing but no blocker immediate!

https://github.com/slackapi/slack-cli/blob/7f39e95b1b755610b3cfc523533f416f8f4d1ba1/.github/workflows/release.yml#L117

[ ] Confirm unit tests and E2E tests are passing on the branch.

👾 https://github.com/slackapi/slack-cli/pull/579

Dominant language
Go
Stars
305
Forks
46
Avg merge
1d 11h
Merged PRs (30d)
23

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from slackapi/slack-cli

All issues in slackapi/slack-cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.