FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Procedure for moving development to nodegit/nodegit · Issue #55 · nodegit/nodegit · GitHub

Repository navigation

Procedure for moving development to nodegit/nodegit #55

Description

Would we just start pushing to nodegit/nodegit and put up a notice on this repo?

Edit I see we can transfer: https://help.github.com/articles/how-to-transfer-a-repository (by we I mean you, I'm not an admin of this repo)

Do you know how we will handle the npmjs side of things?

Activity

  1. Grigore147 commented on Mar 17, 2013

  2. tbranyen commented on Mar 18, 2013

    Member

    We should think about this once the project gets stable again. Too much in flux, don't want to add this into the mix just yet.

  3. faceleg commented on Mar 18, 2013

    CollaboratorAuthor

    👍

  4. ghost assigned on Mar 25, 2013
  5. tbranyen commented on Jun 8, 2013

    Member

    Now that GitHub can redirect seamlessly I have zero objection to doing this whenever. Do I have to pull the plug, or can you do this @faceleg ?

  6. faceleg commented on Jun 15, 2013

    CollaboratorAuthor

    I think you might have to do it, will issues go too?

  7. tbranyen commented on Jun 15, 2013

    Member

    Sweet, done!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


    Back | FazBrowse Home | New Git URL