Remaining work for API Completeness

[HowardWolosky]

Using a single issue to track the remaining work, so as not to litter the Issues and give the wrong impression on the current state of the project, bug wise.

If a contributor is interested in making progress towards any of these items, they should just create a new Issue to track that specific work, mention this Issue, and then resolve their PR against the Issue that they created. At that point, I'll go ahead and update this list and check off that item.

Using a single issue to track the remaining work, so as not to litter the Issues and give the wrong impression on the current state of the project, bug wise.

If a contributor is interested in making progress towards any of these items, they should just create a new Issue to track that specific work, mention this Issue, and then resolve their PR against the Issue that they created. At that point, I'll go ahead and update this list and check off that item.

• Activity
  • Core
  • Events (Issue Events are already supported)
  • Feeds
  • Notifications
  • Starring
  • Watching
• Gists
  • Core
  • Comments
• Git Data
  • Blobs
  • Commits
  • Refs
  • Tags
  • Trees
• Issues
  • Core
  • Assignees
  • Comments
  • Events
  • Labels
  • Milestones
  • Timeline
• Migrations
  • Orgs
  • Source Imports
  • Users
• Miscellaneous
  • Codes of Conduct
  • Emoji
  • Gitignore
  • Licenses
  • Markdown
  • Meta
  • Rate Limit
• Organizations
  • Core (partially done)
  • Blocking Users
  • Blocking Users
  • Members
  • Outside Collaborators
  • Webhooks
• Projects
  • Core
  • Cards
  • Collaborators
  • Columns
• Repositories
  • Core
  • Branches
  • Collaborators
  • Comments
  • Commits
  • Community
  • Contents
  • Keys
  • Deployments
  • Downloads
  • Forks
  • Invitations
  • Merging
  • Pages
  • Releases
  • Statistics
  • Statuses
  • Traffic
  • Webhooks
• Pull Requests (see Complete API support for Pull Requests #175)
  • Core (partially done) (see Complete API support for Pull Requests #175)
  • Reviews (see Complete API support for Pull Requests #175)
  • Review Comments (see Complete API support for Pull Requests #175)
  • Review Requests (see Complete API support for Pull Requests #175)
• Reactions
• Search
• Teams
  • Core (partially supported)
  • Discussions
  • Discussion Comments
  • Members

[HowardWolosky]

@etgottli added Milestone support for Issues with #62

[HowardWolosky]

@joseartrivera added Label support for Issues with #59

[iamraghavs]

I would like to contribute to this. How do I find out whether someone has already taken up an issue? Is that status tracked somewhere?

[HowardWolosky]

Awesome. We'd love to have you. Going forward, all status is being tracked right here on GitHub. If there's something that you'd like to tackle, please go ahead and create a separate Issue tracking that specific item, and assign it to yourself, then start working on it. I thought that given the quantity of items in the checklist above, I didn't want to create individual Issues until we knew they were being covered by someone.

[iamraghavs]

@HowardWolosky I would like to propose that we add a "Create/Update/Delete" branch utility. Branches are currently mentioned under refs which I believe isn't intuitive to the user. Thoughts?

[HowardWolosky]

@raghav710 -- The list above is simply tracking the API set that remains to be implemented, not necessarily indicating what the function names would be. For refs, I would imagine that the functions would use API-based names (e.g. Get-GitHubReference, Create-GitHubReference, etc...) but those would also be aliased-out to names that might make more sense to users, as you suggest (like Get-GitHubBranch, Create-GitHubBranch, etc...)

[HowardWolosky]

#110 now tracking Releases support.