Project migration issue could include shields?
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 11
- Forks
- 4
- Avg merge
- 1h 49m
- Merged PRs (30d)
- 2
Description
It's an optional step, but new projects might like to know about the shields discussed in #72.
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 reading issue #72 and locating the project migration documentation. Determine where optional migration steps are described, then document the relevant shields for new projects. Done means the migration guidance mentions the shields clearly and links or reflects the discussion in #72.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100