googleapis / googleapis/release-please-action
Was this repository recently moved?
- Dominant language
- TypeScript
- Stars
- 2.5k
- Forks
- 327
- PR merge metrics
- No merged PRs in 30d
Description
Thanks for stopping by to ask us a question! Please make sure to include:
- What you're trying to do: Run releases using `google-github-actions/release-please-action`.
- What code you've already tried: What we've been running.
- Any error messages you're getting: This repo is now under `googleapis/release-please-action`. GitHub Actions _does not_ follow redirects when resolving a `uses` action. This has broken quite a bit of our deployment pipeline for many repos and orgs we've setup. Next time, we'll fork just to be safe, but if this was recently moved I'm not sure if you folks are aware of how this breaks GHA workflows. Ideally you should deprecate the old repository, and then fork to the new org, with documentation on where things will be released going forward.
Edit: It's also worth noting, your README is not even updated to include this org name change, yet. So, I'm hoping this was a mistake and can be reverted.
**PLEASE READ**: If you have a support contract with Google, please create an issue in the [support console](https://cloud.google.com/support/) instead of filing on GitHub. This will ensure a timely response.
Contributor guide
Research direction
Start by checking the current README and references to google-github-actions/release-please-action, then verify how the repository move affects GitHub Actions uses paths. Confirm the supported repository location and document the migration or deprecation guidance in the README; done means users can update workflows without relying on redirects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, documentation, release
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100