Skip to content

simplify contributing process #26

Description

@bbodenmiller

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.

Activity

  1. mdda commented on Nov 9, 2015

    @mdda

    As a timesaver, I wrote up the process in a blog post (mostly because compared to GitHub, the process is poor).

  2. vrv commented on Nov 9, 2015

    @vrv

    Thanks! We'll use this bug to track the improvements to the contribution process, which we are working on improving.

  3. bhack commented on Nov 9, 2015

    @bhack
    Contributor

    👍

  4. bhack commented on Nov 10, 2015

    @bhack
    Contributor

    This Github Gerrit plugin could be evaluated

  5. bhack commented on Nov 10, 2015

    @bhack
    Contributor

    /cc @lucamilanesio for the plugin

  6. bhack commented on Nov 21, 2015

    @bhack
    Contributor

    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.

  7. bhack commented on Nov 21, 2015

    @bhack
    Contributor
  8. bhack commented on Dec 12, 2015

    @bhack
    Contributor

    @vrv github history/log is full of "TensorFlow: Merging changes from internal". Not very readable.

  9. martinwicke commented on Dec 12, 2015

    @martinwicke
    Member

    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)
    .

  10. bhack commented on Dec 12, 2015

    @bhack
    Contributor

    @martinwicke Google
    ExoPlayer
    like github management could be a starting point.

  11. vrv commented on Dec 15, 2015

    @vrv

    @bhack: fixed our scripts to have more informative / separate commits: https://github.com/tensorflow/tensorflow/commits/master

    Hope that helps a bit.

  12. bhack commented on Dec 15, 2015

    @bhack
    Contributor

    @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?

  13. bhack commented on Dec 15, 2015

    @bhack
    Contributor

    The last commit seems to have the same description 091ed8c

  14. vrv commented on Dec 16, 2015

    @vrv

    @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.

  15. 21 remaining items

  16. added a commit that references this issue on Mar 12, 2019
  17. added a commit that references this issue on Feb 1, 2021
  18. added 5 commits that reference this issue on Apr 9, 2025
  19. added 2 commits that reference this issue on Mar 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions