Migrate to Publish to BCR actions workflow
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github-actions
- Domain
- build-system, ci-cd, release
Research direction
Start by inspecting the repository's GitHub Actions configuration and the publish-to-bcr documentation linked in the issue. Replace the deprecated publishing integration with the documented workflow, then verify that the configuration supports future module publishes without relying on the GitHub app.
Written by the indexing model from the issue text.
Description
The GitHub app for publishing modules to the BCR is now deprecated. Please consider upgrading to the new GitHub Actions workflow so that future publishes will continue to work.
See the documentation at https://github.com/bazel-contrib/publish-to-bcr.
Let me know if you need any assistance with the migration.
- Dominant language
- Java
- Stars
- 8
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bazelbuild/bazel-worker-api
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
bazelbuild/bazel-worker-api#14 · 3 comments ·
All issues in bazelbuild/bazel-worker-api
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
openhab/openhab-core#5847 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
apache/parquet-java#3820 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
beehive-lab/jllm#187 ·