WordPress / WordPress/two-factor
Document process for pre-releases
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 825
- Forks
- 187
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 17
Description
We should document the proper way how to do pre-releases/betas for two-factor.
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or documentation entry points are named in the issue. Start by locating the repository's existing release documentation and reviewing how pre-releases or betas are handled for the two-factor WordPress plugin. Done means the proper pre-release process is documented clearly enough for maintainers to follow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- authentication, documentation, release
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- Half a day
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100