You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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).
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.
The text was updated successfully, but these errors were encountered: