#7 track forks

0.4
closed
nobody
feature (22)
2014-05-13
2012-05-07
Christian Weiske
No
  1. Whenever a paste is forked, keep track of it.
  2. Link to parent paste
  3. Link to child pastes.

We already keep track of their git url since we clone from them. What we don't keep track of is titles of remote pastes. I imagine something along a "git config remote.origin.title 'Foo'" call to keep the title of the remote paste in the config, independent from the database.

Related

Tickets: #21

Discussion

    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1,3 +1,5 @@
     1. Whenever a paste is forked, keep track of it.
     2. Link to parent paste
     3. Link to child pastes.
    +
    +We already keep track of their git url since we clone from them. What we don't keep track of is titles of remote pastes. I imagine something along a "git config remote.origin.title 'Foo'" call to keep the title of the remote paste in the config, independent from the database.
    
     
  • --DELETED--

     
    Last edit: Justin J. Novack 2012-10-07
  • And for child forks, if phorkie forks it, or we get a pingback, create a remote.timestamp.url Perhaps timestamp+msec? or +hash of something?

    If a phorkie repo has a remote.origin.url (see above), with type=phorkie, then call /delete-fork/origin/thischild to clean up the original repository (optional, but recommended).

    This way, I can fork a repo from you, and you'll have it in your git config. When I delete my fork, yours can be cleaned up.

     
    Last edit: Justin J. Novack 2012-10-07
  • Yes, that's the idea. type=phorkie should be type=fork. timestamp+msec can be replaced with a php uniqid() since there is no meaning in that name anyway. Alternatively we could use the rawurlencoded remote url as name.

     
  • 3/4 of the feature is implemented in git.

     
  • Implemented in git master

     
    • status: open --> closed
    • Milestone: future --> 0.4