[–] talmirza 13y ago ↗ I have written a lot of code for OS that doesn't get committed into master.I was wondering what I could do to improve my code written to code committed ratio.Still open to suggestions. [–] jff 13y ago ↗ Write highly detailed commit messages.Email the owner to discuss what you're adding and why, especially if it's a big thing.Keep your commits small--nothing worse than a mega-commit which fixes 3 different bugs and updates the formatting for 10 files.Make sure to follow the project's formatting and naming conventions. [–] jeremyjh 13y ago ↗ Also make sure you update and add relevant tests and documentation. [–] [deleted] 13y ago ↗ (comment deleted)
[–] jff 13y ago ↗ Write highly detailed commit messages.Email the owner to discuss what you're adding and why, especially if it's a big thing.Keep your commits small--nothing worse than a mega-commit which fixes 3 different bugs and updates the formatting for 10 files.Make sure to follow the project's formatting and naming conventions. [–] jeremyjh 13y ago ↗ Also make sure you update and add relevant tests and documentation.
[–] jonchang 13y ago ↗ The pull request referenced in the post can be seen here: https://github.com/twitter/bootstrap/pull/6127
5 comments
[ 1.1 ms ] story [ 22.6 ms ] threadI was wondering what I could do to improve my code written to code committed ratio.
Still open to suggestions.
Email the owner to discuss what you're adding and why, especially if it's a big thing.
Keep your commits small--nothing worse than a mega-commit which fixes 3 different bugs and updates the formatting for 10 files.
Make sure to follow the project's formatting and naming conventions.