Lines Matching full:you
3 Thank you for your interest in contributing to the Apache Thrift project! Information on why and h…
11 This is the preferred method of submitting changes. When you submit a pull request through github,
18 1. All pull requests should contain a single commit per issue, or we will ask you to squash it.
37 …* Verify that you follow [Thrift Coding Standards](/docs/coding_standards) (you can run 'make styl…
38 …arted/#Step-one%3A-Sign-in) and [AppVeyor](http://www.appveyor.com/docs). You can use this techni…
44 …1. Wait for a committer to commit your patch. You can nudge the committers if necessary by sendin…
46 ## If you want to build the project locally ##
54 ## If you want to review open issues... ##
57 …r](http://issues.apache.org/jira/browse/THRIFT). You can search for tickets relating to languages…
59 ## If you discovered a defect... ##
62 1. If not, create a ticket describing the change you're proposing in the Jira issue tracker.
71 … changes and incurs additional overhead for committers who must then create a pull request for you.
75 …you to take actions in your pull requests. Here are some recipes that will help you accomplish th…
79 …you have not submitted a pull request yet, or if you have not yet rebased your existing pull reque…
81 1. Use the command ``git log`` to identify how many commits you made since you began.
87 If you already have a pull request outstanding, you will need to do a "force push" to overwrite it …
104 If your pull request contains commits that are not yours, then you should use the following techniq…
114 …your commits in order to the current master, then you will squash them to a single commit, and the…