Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow selecting specific tags/revisions/branches from the corresponding repository #8

Open
armish opened this issue Mar 6, 2014 · 2 comments

Comments

@armish
Copy link

armish commented Mar 6, 2014

Currently, by default, the submission system does not distinguish between branches, tags or revisions of a project that is to be submitted to FigShare.

Most development teams take advantage of branches to isolate releases and development branches (see A successful Git branching model).

In regards to this, my humble suggestion is to list tags and branches in a project whenever a user initiates a submission. This way people will, for example, able to say: "I want my latest stable code to submitted to FigShare", which provides incredible flexibility for submissions and this model will better with the current established development strategies.

@hubgit
Copy link
Member

hubgit commented Mar 6, 2014

I hope that we'll simply be able to settle on using releases as the objects to be archived (and as you suggest, figshare would watch for new releases ("stable code") and archive them automatically).

@robldavidson
Copy link

@hugbit That is how Zenodo appears to work currently. Seems like a decent system for integration with GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants