Skip to content

feat(chore): add troubleshooting guide#64

Open
camillecroft wants to merge 2 commits into
mainfrom
chore/add-troubleshooting-doc
Open

feat(chore): add troubleshooting guide#64
camillecroft wants to merge 2 commits into
mainfrom
chore/add-troubleshooting-doc

Conversation

@camillecroft
Copy link
Copy Markdown
Contributor

Added a troubleshooting guide based on recent issues encountered in the csda-data-monitoring repo.

@camillecroft camillecroft requested a review from a team May 27, 2026 15:50
@camillecroft camillecroft requested a review from emmalu as a code owner May 27, 2026 15:50
Comment thread docs/troubleshooting.md
Comment on lines +36 to +49
If the release-please action fails, it never removes the `autorelease: pending` label. This causes release-please to ignore any workflow changes and continuously retries the failed release.

#### Examples

- You update `release-as` in your workflow to a new version, but release-please keeps trying to create the old version
- Release-please workflow runs but ignores your configuration changes
- You see the error message `Resource not accessible by integration` or permission errors in the workflow logs

#### Solution

- Find the Release PR that failed with the `autorelease: pending` label
- Manually remove the `autorelease: pending` label from the PR
- Re-run the release-please workflow
- This clears release-please's "memory" of the failed release and allows it to read your updated configuration No newline at end of file
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Oh, this is helpful to learn! 🙌🏽

Comment thread docs/troubleshooting.md
@@ -0,0 +1,49 @@
# Troubleshooting Guide

#### Required Workflow Permissions
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
#### Required Workflow Permissions
## Required Workflow Permissions

nit: headings should only increment +1

Comment thread docs/troubleshooting.md

#### Required Workflow Permissions

Ensure your `.github/workflows/release-please.yml` file includes the following permissions:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Could we do a short intro on when this guide is relevant (because a release-please.yml workflow is required in each repo)? A pointer to the wiki page could also be helpful.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

💯

Copy link
Copy Markdown
Contributor

@emmalu emmalu left a comment

Choose a reason for hiding this comment

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

This generally LGTM, although I'd be curious if @gadomski can think of any other common issues to work through?

Comment thread docs/troubleshooting.md

#### Verify CSDA Release App Access

- Visit the [CSDA Release App installations page](https://github.com/apps/csda-release-app/installations/105597643)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
- Visit the [CSDA Release App installations page](https://github.com/apps/csda-release-app/installations/105597643)
- Visit the [CSDA Release App installations page](https://github.com/apps/csda-release-app) and follow the authentication steps to `Configure`

nit: I think it's nice to document the main app URL (otherwise it's hard to find!) but pointing to the specific "installation" seems unnecessary.

Copy link
Copy Markdown
Contributor

@gadomski gadomski left a comment

Choose a reason for hiding this comment

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

LGTM!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants