fix: automate publishing and package versioning #104
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
Contributor
|
@jbadan you are part of the contributors so you don't have to use forks |
bcullman
added
the
contribution welcome
Contributor
|
we are looking for help setting to Help move this PR forward. |
Contributor
Author
|
Closing in favor of #140 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello from SAP Concur! 👋
Related to #78:
Here is a quick example of automating package versioning using
standard-versionand publishing thedistfolder + other necessities when you merge to master.This will not work as travis still needs to be configured as well as the Github build username/email combo.
Feel free to close as this is not currently functional and there are tons of ways to do this, just wanted to give an example.