- Sort Score
- Result 10 results
- Languages All
Results 1 - 3 of 3 for prs (0.16 sec)
-
CONTRIBUTING.md
Making and Submitting Changes -------------- We accept Pull Requests via GitHub. The [developer mailing list][dev-ml-list] is the main channel of communication for contributors. There are some guidelines which will make applying PRs easier for us: + Create a topic branch from where you want to base your work (this is usually the master branch). Push your changes to a topic branch in your fork of the repository. + Make commits of logical units.
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Sun Oct 10 09:48:27 GMT 2021 - 4.7K bytes - Viewed (0) -
CONTRIBUTING.md
* [Sign off your commits](https://git-scm.com/docs/git-commit#Documentation/git-commit.txt---signoff) to indicate that you agree to the terms of [Developer Certificate of Origin](https://developercertificate.org/). We can only accept PRs that have all commits signed off. * Keep commits discrete. Avoid including multiple unrelated changes in a single commit.
Plain Text - Registered: Wed Apr 24 11:36:11 GMT 2024 - Last Modified: Fri Feb 09 15:30:53 GMT 2024 - 15.6K bytes - Viewed (0) -
CONTRIBUTING.md
airtime before a decision is made regarding whether they are to be migrated to the core. * As every PR requires several CPU/GPU hours of CI testing, we discourage submitting PRs to fix one typo, one warning,etc. We recommend fixing the same issue at the file level at least (e.g.: fix all typos in a file, fix all compiler warnings in a file, etc.) * Tests should follow the
Plain Text - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Thu Mar 21 11:45:51 GMT 2024 - 15.6K bytes - Viewed (0)