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

Start Using Releases on Github #51

Open
ctsstc opened this issue May 28, 2018 · 1 comment
Open

Start Using Releases on Github #51

ctsstc opened this issue May 28, 2018 · 1 comment

Comments

@ctsstc
Copy link

ctsstc commented May 28, 2018

Problem

  • There are currently no releases on github or tags on this repository.
  • There does seem to be versioning within the package.json.

Reasoning

  • This allows for snapshots and marks a time within commits that a certain code was a specific version.
  • This allows for more accurate issues, you can more easily compare code against a specific version.

Solution

Thoughts

  • You may be able to tag older commits, but I think you can only create releases on github for the latest commit on master.
@drewjbartlett
Copy link
Collaborator

@ctsstc thanks for making this. Is this in any way related to when I have to tag each version commit? By doing npm version patch it adds the version tag to that commit. This is separate I assume?

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

2 participants