[PR #38] [MERGED] add travis ci #499

Closed
opened 2026-02-25 23:34:31 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/go-shiori/shiori/pull/38
Author: @ddulic
Created: 3/3/2018
Status: Merged
Merged: 3/5/2018
Merged by: @RadhiFadlillah

Base: masterHead: travis


📝 Commits (1)

📊 Changes

1 file changed (+39 additions, -0 deletions)

View changed files

.travis.yml (+39 -0)

📄 Description

Add the option to deploy releases via Travis CI deployments for linux, osx and windows binaries.

If you haven't used travis before just create an account on https://travis-ci.org/ connect and enable this github repo. Should be self explanatory.
One thing you will have to do is add your $TOKEN via travis env variables. You have multiple ways of doing this which you can read here
I used Defining Variables in Repository Settings in my example.

Once you have configured everything simply tag releases as you did before and travis will create a release on every tagged commit :)

Hopefully this will be of some use 👍


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/go-shiori/shiori/pull/38 **Author:** [@ddulic](https://github.com/ddulic) **Created:** 3/3/2018 **Status:** ✅ Merged **Merged:** 3/5/2018 **Merged by:** [@RadhiFadlillah](https://github.com/RadhiFadlillah) **Base:** `master` ← **Head:** `travis` --- ### 📝 Commits (1) - [`da03aff`](https://github.com/go-shiori/shiori/commit/da03aff6303c9dff2a7b71de8dc4997c53f070bf) add travis ci ### 📊 Changes **1 file changed** (+39 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `.travis.yml` (+39 -0) </details> ### 📄 Description Add the option to deploy releases via Travis CI deployments for linux, osx and windows binaries. If you haven't used travis before just create an account on https://travis-ci.org/ connect and enable this github repo. Should be self explanatory. One thing you will have to do is add your `$TOKEN` via travis env variables. You have multiple ways of doing this which you can read [here](https://docs.travis-ci.com/user/environment-variables/) I used [Defining Variables in Repository Settings](https://docs.travis-ci.com/user/environment-variables/#Defining-Variables-in-Repository-Settings) in my example. Once you have configured everything simply tag releases as you did before and travis will create a release on every tagged commit :) Hopefully this will be of some use :+1: --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-02-25 23:34:31 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/shiori#499
No description provided.