Skip to content

Remaining work for API Completeness #70

@HowardWolosky

Description

@HowardWolosky
Contributor

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

added
enhancementAn issue or pull request introducing new functionality to the project.
api completenessThis is basic API functionality that hasn't been implemented yet.
help wantedAnyone in the community is welcome to do this work
good first issueIf you're new to the project (or to OSS in general) and you'd like to contribute, try this one.
on Dec 11, 2018
HowardWolosky

HowardWolosky commented on Dec 13, 2018

@HowardWolosky
ContributorAuthor

@etgottli added Milestone support for Issues with #62

HowardWolosky

HowardWolosky commented on Dec 13, 2018

@HowardWolosky
ContributorAuthor

@joseartrivera added Label support for Issues with #59

raghav710

raghav710 commented on Dec 14, 2018

@raghav710

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

HowardWolosky commented on Dec 14, 2018

@HowardWolosky
ContributorAuthor

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.

raghav710

raghav710 commented on Feb 19, 2019

@raghav710

@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

HowardWolosky commented on Feb 20, 2019

@HowardWolosky
ContributorAuthor

@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

HowardWolosky commented on May 20, 2019

@HowardWolosky
ContributorAuthor

#110 now tracking Releases support.

11 remaining items

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    api completenessThis is basic API functionality that hasn't been implemented yet.enhancementAn issue or pull request introducing new functionality to the project.good first issueIf you're new to the project (or to OSS in general) and you'd like to contribute, try this one.help wantedAnyone in the community is welcome to do this work

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @raghav710@vercellone@roboaks@giuseppecampanelli@HowardWolosky

        Issue actions

          Remaining work for API Completeness · Issue #70 · microsoft/PowerShellForGitHub