actions / actions/starter-workflows
Enabling autopublish as requested
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12.1k
- Forks
- 7.3k
- PR merge metrics
- No merged PRs in 30d
Description
Enabling autopublish as requested
Originally posted by @simoneonofri in https://github.com/w3c/webcrypto/pull/407
Contributor guide
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.
Research direction
Start by reviewing the originating discussion in pull request #407 and the surrounding repository context for what “autopublish” is expected to mean. The issue does not name files, tests, or acceptance criteria, so confirm the intended workflow and define completion with the maintainers before making changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 10/100