Skip to content

Git bisync

Git bisync

Categories

JUMP TO ANOTHER FORUM

(thinking…)

How can we improve the alpha git bisync?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

14 results found

  1. Git SSH Support

    Currently, Git Sync only supports HTTP(S) protocol, with username/password login. Support should be added for the SSH protocol. Pursuant to this, allow providing an SSH key-pair for authentication as an alternative to username/password when using SSH.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. GitSync: LFS support

    Add LFS support to gitsync so that we can sync git repos that use LFS.

    12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  3. Add possibility to gitsync in sync view

    Allow user to setup gitsync in sync view.
    It's useful for synchronizing xlinks with git.

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  4. ignore, gitignore and **

    Does ignore.conf accept **? I need to use this wildcard when converting gitignore files.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  5. Allow us to only do pull or push when syncing my repository

    I'm using GitSync and I'm loving the idea of using Plastic as a front end to Git.
    But I'm pretty sure that if I manage to only pull or push changes when syncing it would be A LOT better.
    Sometimes I don't want to push my checkins without ending my tasks... :)

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  6. Author email addresses

    After syncing with a github repository the author email addresses aren't set to anything. E.G. "deangardiner <deangardiner@.(none)>"

    This means github isn't able to link users with commits which ultimately breaks my usual workflow.

    Is this a known issue? or is there a way to set the email address of authors that I'm not able to find?

    14 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    under review  ·  4 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  7. User mapping for GitSync

    It'd be nice to be able to map git users/owners of changesets/commits to plastic users. I think you already support this kind of mapping elsewhere doing replications and imports/exports.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  8. Sync code reviews to GitHub

    Would it be possible to also have GitSync synchronize plastic code reviews (line comments) to GitHub? Or is that too specific to github? Maybe this can be enabled by activating a third-party hook in GitHub to another system that does code reviews .. ? (Or better yet, plastic could expose its own hook for code reviews so people can mash it up with any service they want).

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  9. Permissions check before starting sync.

    Not super critical but I have noticed that when i run a sync that requires actions that my user account doesn't have access to do like "make top-level branch", it goes through the sync until it tries to do that task and then cancels the whole sync. This is leaves a partial sync done.

    I thought maybe a good idea would be to gather all actions/tasks necessary up-front to do the sync, run each action against permissions check, and not allow the sync to continue if they dont have all permissions.

    alternatively, part of the git-sync configuration could be to…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  10. Doing a git sync using the VS plugin causes Visual Studio to Crash

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    started  ·  2 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  11. Partial Sync

    It looks like there are some issues with syncing large repositories to plastic. It would be good if you could do a partial time-limited sync. You could enter a date range and only sync the data between this range.

    Similarly, it would be nice to have the option to only sync a single branch such as main / master when you're pulling information from your git repo.

    15 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    3 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  12. Allow the user to cancel or stop the Sync process

    Hi!
    I was testing the import the mono repo from github yesterday and it took a lot of time to even get to 50% done.
    Would be really cool if we could cancel the operation or stop it and start again (even if the have to download the data again).
    Or maybe make the sync operation run in the background not on modal.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    3 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  13. ignore.conf and .gitignore

    They don't have the same syntax, so it would be nice to have a conversion method (.gitignore -> ignore.conf) taking recursively into account all the .gitignore files in the source tree. In fact, I wanted to try :) but I've not been able to find a detailed syntax of ignore.conf...

    44 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    3 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  14. Disassociating the repo from a given git remote

    I have successfully synced with a Bitbucket test repo, but when I try to do the same with the "real" repo I find that Plastic stores somewhere that it is associated with the test repo. The message is: "Error: The settings you've introduced don't match with the stored ones for branch/repo default. Stored are: git https://
    icalvo@bitbucket.org/icalvo/icm.test.git". How can I make Plastic to forget it?

    15 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    5 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
  • Don't see your idea?