release-please: Unhelpful "not found" message when running on private repo
Environment details
- OS: Ubuntu 18.04.5 (GitHub Workflow)
- Node.js version: n/a
- npm version: n/a
release-pleaseversion: v1.3.0
Steps to reproduce
- Use the sample
release-please.ymlworkflow from the README in a private Node.js repository that has had zero releases so far. - Push a commit to the repository.
- Get this output:
Run GoogleCloudPlatform/release-please-action@v1.3.0
✖ no recent release PRs found
✔ found 6 commits since undefined
✖ branch release-v1.0.0 already exists
✖ CHANGELOG.md not found
✔ creating CHANGELOG.md
✔ updating package.json from 0.0.0 to 1.0.0
✔ updating package-lock.json from 0.0.0 to 1.0.0
✖ file samples/package.json did not exist
Error: release-please failed: Not Found
What does that last “Not Found” mean?
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 1
- Comments: 16 (14 by maintainers)
@abeMedia perhaps a better idea, would you be able to invite me to a fake private repository that’s exhibiting the issue?
Looks like it was our company issue
this is possible still issue with latest version google-github-actions/release-please-action/issues/262 on my private repo I didn’t see this issue, but within the organisation repo I have the same with the latest version