awesomewm-mirrors
/
awesome-www
mirror of https://github.com/awesomeWM/awesome-www.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

doc(readme; doing_a_release): replace travis to gh-actions

This commit is contained in:
actionless 2022-06-26 22:10:08 +02:00
parent 0d6631d04a
commit b782b4fca3
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -1,6 +1,6 @@
# Website for awesome WM
[![Build Status](https://travis-ci.org/awesomeWM/awesome-www.svg?branch=master)](https://travis-ci.org/awesomeWM/awesome-www)
[![Build Status](https://github.com/awesomeWM/awesome-www/actions/workflows/www.yml/badge.svg)](https://github.com/awesomeWM/awesome-www/actions/workflows/www.yml)
This is the main source of the
[website for the awesome window manager](https://awesomewm.org/).
@ -74,7 +74,7 @@ section in `recipes.mdwn` file.
## Publishing
The master branch gets built by
[Travis CI](https://travis-ci.org/awesomeWM/awesome-www/), and is then published
[GH Actions](https://github.com/awesomeWM/awesome-www/actions), and is then published
through
[Github's Organization Pages](https://github.com/awesomeWM/awesomeWM.github.io).

2
doing_a_release.mdwn
View File

@ -31,7 +31,7 @@ The following steps are done in a checkout of the *awesome-www* git repository.
* In the awesome-www repository (push just the release branch!)
* In the awesome repository (make sure the tag is also pushed!)
* Create a pull request to the awesome-www repository for the release branch.
This makes sure that the Travis build will be successful when merging into the
This makes sure that the Github-Actions build will be successful when merging into the
master branch.
* Create the release on GitHub:
* Go to the GitHub release page <https://github.com/awesomeWM/awesome/releases/new>.