![auto shipit auto shipit](https://static.wixstatic.com/media/865215_e22d67aac611485b88c8606b1c0db37d~mv2.jpg)
Generate releases based on semantic version labels on pull requests, and
![auto shipit auto shipit](https://fretcot.com/wp-content/uploads/2021/02/IMG_5691-1536x1152.jpg)
#Auto shipit code#
To version, changelog, publish and release your code all at the same time we've included the shipit tool. GH_TOKEN=YOUR_TOKEN auto create-labelsĪuto is written so that each tool it exposes is useful in isolation. To create the labels for your project on GitHub, run the following command with your GH_TOKEN. These are customizable too, and you can even add your own sections.
![auto shipit auto shipit](https://www.autoshippers.co.uk/images/shipit-usp/faster-white.jpg)
You can also store these values in a local file at the root of your project named. GH_TOKEN - Used for updating the changelog and publishing the GitHub release.You must configure some environment variables for publishing and releasing to work properly. Merged with `/graphql` to build the final URL. `githubApi`, you can use `githubGraphqlApi` to set the base path for `auto`. GithubGraphqlApi If you are using enterprise github and your company hosts the graphql at some other URL than the GithubApi If you are using enterprise github, `auto` lets you configure the github API URL that it uses. autorc than with a flag: baseBranch Configure what your repo considers the base branch. The following are options that might be more useful to set in the. autorc will get overridden by the CLI flags if provided. autorc and do not exist as CLI flags.Īny option in the. autorc options you supply them in camelCase (fooBar),Įxclusive options (extends, labels) can only be set in the. autorc file.Īs CLI options you supply them in snake-case (-foo-bar), but as. auto initĪll options can also be configured via the. You can configure most flags and all labels/changelogTitles. If this is not run then auto will use the default configuration. (OPTIONAL) Initialize all options and configure label text. In the Tag version field enter the version number you just tagged and click Publish release. Then on GitHub go to your project's releases and click Draft a new release. To tag your last release find the last commit where you bumped the version and run the following commands with your version number. If your project is already published or has releases then you need to make sure that your last release is tagged and that it's the Latest Release on GitHub.
#Auto shipit install#
npm install autoįor auto installation in non-npm environments follow these instructions. InstallationĪuto is distributed through npm, but you can use it with a variety of package management platforms. While intended to run in a continuous integration (CI) environment, all auto commands can run locally as well. This approach does not require you to change your code or make any drastic changes to your current workflow. It is powered by semantic version labels on pull requests. Auto is a tool designed to seamlessly automate the release workflow.