Update readme

README.md

@@ -7,8 +7,6 @@
 |----------------------------   |------------------|
 | [eralpkaraduman.github.io/cv] | [latest release] |
 
-[![Build Status](https://travis-ci.org/eralpkaraduman/cv.svg?branch=gh-pages)](https://travis-ci.org/eralpkaraduman/cv)
-
 **If you want to have your own, just fork this repo and modify the `index.md`.**
 
 This is a fairly modified version of
@@ -30,16 +28,20 @@ replica of github's markdown style. And it is able to auto-generate a PDF versio
 
 ## Automatic PDF version generation
 
-Also if you set up Travis CI, i configured it up so after every commit, travis will print it to `cv.pdf` then create a release on github. You can always link to the latest release by adding the sufffix `/releases/latest` to repo url.  
+If you configure the GitHub Action, it creates a pdf version then create a release on github. You can always link to the latest release by adding the sufffix `/releases/latest` to repo url.  
 For example;  
 github.com/your-username-here/cv[/releases/latest](https://github.com/eralpkaraduman/cv/releases/latest)
 
 To enable this;  
 - Go to [github.com/settings/tokens](https://github.com/settings/tokens)
 - Generate a personal access token, give it `public_repo` permission
-- Go to travis-ci.org settings page of you repo
-- Enter the token as Environment Variable with the key `GITHUB_OAUTH_TOKEN`
-- If everything was right, it will create a release under `/releases` page of your github repo
+- Go to the secrets settings of this github repo (the one that is your clone)
+  - https://github.com/<your gh username>/cv/settings/secrets/actions
+  - Remember to change the username in the url above
+- Click "New repository secret" 
+- Name it `GH_OAUTH_TOKEN`
+- Paste the token you generated in the earlier step here
+- Next time you make a change, it should create a new release under `/releases` page of your github repo
 - Latest release is conveniently always at `/releases/latest`
 
 
@@ -52,7 +54,7 @@ This link won't be generated in the PDF itself for several reasons;
 - Lack of necessity, since you have the pdf there's need to download it again.
 - I didn't want to deal with all the troubles coming with executing javascript in pdf generation context
 - Travis CI blocks the request to github API i guess?
-- I disabled javascript for wkhtmltopdf, see 2 reasons above.
+- I disabled javascript on wkhtmltopdf, see 2 reasons above.
 
 
 ## Running jekyll locally