Should we including the following 2 methods in V1? revokePullRequestByID aprovePullRequestByID
On Wed, Jun 11, 2014 at 5:49 PM, Rasika Hettige <[email protected]> wrote: > *Introduction* > The Bitbucket REST API allows third-party application developers the means > for writing applications for the Bitbucket service. Our REST API is based > on > open standards, you can use any web development language to access the API. > Using the API, users can sign in and grant your application the right to > make calls on their behalf. Then, through the API, your application can > access Bitbucket resources such as an individual (or team) account, > repositories, and aspects of these resources such as changesets or > comments. > > *API* > > https://confluence.atlassian.com/display/BITBUCKET/Use+the+Bitbucket+REST+APIs;jsessionid=34852CBC70565AD39156EA091CE47A4D.node1 > > *BigBucket Connector Summary* > • Connector Name: bigbucket-connector-1.0.0 > • Version: 1.0.0 > • Technology: REST > > *Authentication* > To authenticate, it uses OAuth 1.0a > > *Methods Selected:* > > *Pull Requests* > *listPullRequest* - Get a list of of a repository's open pull requests. > *createPullRequest* - Creates a new pull request. The request URL you > provide is the destination repository URL. For this reason, you must > specify > an explicit source repository in the request object if you want to pull > from > a different repository. > *getPullRequest* - Gets an specific pull request. > *updatePullRequest* -Updates an existing pull request. The pull request's > status must be open. > *mergePullRequest* - Accept a pull request and merges into the destination > branch. This requires write access on the destination repository. > *discardPullRequest* - Rejects a pull request. This requires write access > on > the destination repository. > *listPullRequestComments* - Gets the array of comments on the specified > pull > request. > *getPullRequestDiff* -Gets the diff or patch for a pull request. > > > *Repositories* > *getRepository* - Returns a single repository. > *createRepository* - To create a new repository, POST directly to the > desired URL, providing a JSON request body that contains the properties of > the new repository. > *deleteRepository* - Removes a repository. > > *Commits* > *listCommits* - Gets the information associated with an individual commit. > *listCommitComments* - Gets the array of comments on the specified pull > request. > > *Methods Not Selected:* > > Methods under following categories are not selected. > Branch restriction > Teams > Users > > And also following administration functionalities are not considered. > > getPullRequestActivityList > getPullRequestActivityByID > getPullRequestCommits > revokePullRequestByID > aprovePullRequestByID > getPatchSpecification > getRepositoryFolks > getRepositoryWatches > setApprovalOnCommit > revokeApprovalOnCommit > > > getPullRequestCommentByID - The functionality of following method can also > be achieved through "getPullRequestComments" > getCommitComments - The functionality of following method can also be > achieved through "listCommitComments" > > > Thanks & Regards > Rasika > > > > -- > View this message in context: > http://wso2-oxygen-tank.10903.n7.nabble.com/Connector-BitBucket-tp98058.html > Sent from the WSO2 Architecture mailing list archive at Nabble.com. > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > -- Shevan Goonetilleke Director of Engineering WSO2, Inc. lean.enterprise.middleware m: +94777340680 w: http://wso2.com
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
