Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
P
purr-data
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 403
    • Issues 403
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 38
    • Merge Requests 38
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Jonathan Wilkes
  • purr-data
  • Issues
  • #429

Closed
Open
Created Mar 23, 2018 by Albert Gräf@aggraefDeveloper

https://github.com/jonwwilkes/purr-data is out of sync

Jonathan, you forked https://github.com/jonwwilkes/purr-data from my GH mirror at https://github.com/agraef/purr-data in order to upload your releases. Which is all good and fine, but you never sync that repo with upstream, and so your release tags at https://github.com/jonwwilkes/purr-data/releases all point to the same long out-of-date revision 1f41004d. (In case you're wondering, that's also why it says on the overview page that "This branch is 366 commits behind agraef:master.")

I wouldn't be worried about this, but I see that your repo there has been forked at least two times already, so at least some people seem to think that it is the real thing, when it's just an out-of-date clone being used as a download area.

Fixing this is simple. In your local working copy of git@git.purrdata.net:jwilkes/purr-data.git, just add git@github.com:jonwwilkes/purr-data.git as a remote named, say, github. Then, whenever you're about to upload a release, just run git push github. Your fork there will be up-to-date and you can then create the release tag and upload your release on GH to the proper revision.

Assignee
Assign to
3.0.0
Milestone
3.0.0
Assign milestone
Time tracking
None
Due date
None