Skip to content

Add 'Template Cleanup fails in first Workflow' in TROUBLESHOOTING.md #292

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.

Sign up for GitHub

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Add 'Template Cleanup fails in first Workflow' in TROUBLESHOOTING.md #292

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
8fefebd
Add Template Cleanup Section
Smponi Apr 9, 2025
90dfd40
Add Template Cleanup Section
Smponi Apr 9, 2025
8bcaf0e
Add images
Smponi Apr 14, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 15 additions & 1 deletion TROUBLESHOOTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,4 +24,18 @@ FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':library-compose:detekt'.
> Invalid value (20) passed to --jvm-target, must be one of [1.6, 1.8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18]
```
```

# Template Cleanup fails in first Workflow

If the error occurs in the **Push changes** step of the workflow and you encounter errors such as:

```
fatal: unable to access 'https://github.com/<username>/<repo>.git/':
The requested URL returned error: 403
Error: Invalid exit code: 128
```

then the issue is likely due to the workflow permissions of your repository. To resolve this, navigate to your repository settings, go to **Actions -> General**, and set the Workflow Permissions to **Read and Write**.

Once the workflow completes successfully, you can and probably should revert the permissions back to the default settings.
Copy link
Owner

Choose a reason for hiding this comment

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

Are you sure about this? This shouldn't be the case as by default the workflow runs with a token that has read/write access 🤔

Copy link
Author

Choose a reason for hiding this comment

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

Valid observation. In my experience, the default setting is set to no write access, and I haven't changed anything. (I'm not even aware where this default can be modified 😅)

Additionally, some/several users have reported encountering this same behavior in this issue: ad-m/github-push-action#96

Copy link
Owner

Choose a reason for hiding this comment

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

Oh I see. Maybe we should add an image of the settings screen also then?

Copy link
Author

Choose a reason for hiding this comment

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

Fair point!

I've added 4 images. However, I don't really know how the template-feature of GitHub works, so I hope it's correct to put them in a new folder.

Copy link
Owner

Choose a reason for hiding this comment

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

I guess the best would be to use the GitHub assets url (basically the URL you get when you drag and drop an image in a comment box) rather than having the images in the repo as otherwise everyone will copy them (which is not ideal).