Repository navigation
simplify contributing process #26
Description
Activity
As a timesaver, I wrote up the process in a blog post (mostly because compared to GitHub, the process is poor).
Thanks! We'll use this bug to track the improvements to the contribution process, which we are working on improving.
👍
This Github Gerrit plugin could be evaluated
/cc @lucamilanesio for the plugin
Is this googlebot behaviour on other Google projects on github enought to let collect directly PRs here? If you want to get a pass with Gerrit you can also use the Gerrit github plugin I've already mentioned.
Also nice to evaluate is https://github.com/facebook/mention-bot
@vrv github history/log is full of "TensorFlow: Merging changes from internal". Not very readable.
You're correct. We're working on the process. It'll get better.
On Sat, Dec 12, 2015 at 1:57 AM bhack [email protected] wrote:
@vrv https://github.com/vrv github history/log is full of "TensorFlow:
Merging changes from internal". Not very readable.—
Reply to this email directly or view it on GitHub
#26 (comment)
.@martinwicke Google
ExoPlayer like github management could be a starting point.@bhack: fixed our scripts to have more informative / separate commits: https://github.com/tensorflow/tensorflow/commits/master
Hope that helps a bit.
@vrv If you don't rewrite the history and push force now some info will be lost forever here. Related, don't you like the Gerrit plugin I suggested? Why other Google projects like ExoPlayer seems to have a more "natural" relation with github?
The last commit seems to have the same description 091ed8c
@bhack: other projects probably have a more natural relation with github because they only have one source of truth. We have git, and we have our internal repository that we also contribute to actively, so the merge commit is unavoidable when trying to merge two different lineages.
That being said, now that we've moved to individual commits, the merge commit shouldn't be that bad. And it's basically the same as the merge commit from a pull request on github.
21 remaining items
- added a commit that references this issue
on Mar 12, 2019 - added a commit that references this issue
on Feb 1, 2021 - added 5 commits that reference this issue
on Apr 9, 2025 - added 5 commits that reference this issue
on Jul 28, 2025 - added a commit that references this issue
on Nov 26, 2025
Currently the contributing process is rather complex... I have to use another website, clone the repo, and more. I'm just interested in making some minor tweaks to the documentation that normally can be done with just a few clicks using GitHub.