iiitv / iiitv/iiitv.github.com
Issue backend ideas
Open
Nobody has claimed this yet.
discuss
- Dominant language
- HTML
- Stars
- 28
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
GitHub Issues API https://developer.github.com/v3/issues/
- The list issues for a repo function has features like filtering wrt labels and author and sorting so that should be helpful.
- Using parameters
directionandsincewe should be able to list the issues we need at the moment. - Blog should be powered by a separate repository and its issues will only be used for blog posts. This way those issues will not hinder the development process (in this repo).
your views ?? @ansarimofid
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
Start with the linked GitHub Issues API documentation, especially repository issue listing and the direction and since parameters. Clarify whether this repository should consume issue data and whether blog posts belong in a separate repository. Done requires an agreed scope and implementation location, but no files or tests are identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100