Adding CI on Github Actions.

[koh110]

Instructions

Context: #3718 (comment)

Adding CI on Github Actions.

PRs have also stopped CI around June. I think Travis CI needs to be migrated to another domain.
I don't know the CI migration plan for the axios project.
So, I added CI on Github Actions until CI worked again.

Additional context

#3930
#3916

[koh110]

@jasonsaayman @emilyemorehouse
Hi! Could you check it please?

It seems that you are the most active maintainers.
If you should ping another maintainer, please let me know.

Thanks.

[jasonsaayman]

Hi, Thanks I will do, I will be more active again in the weeks to come.

[koh110]

@jasonsaayman Thanks! I hope that the axios project will move forward.
Please let me know if you have any help.

[jasonsaayman]

@koh110 seems to have passed however I don't see how we are going to handle browser based testing?

[jasonsaayman]

@koh110 seems to have passed however I don't see how we are going to handle browser based testing?

Don't worry, I have answered my own question

[jasonsaayman]

@koh110, thanks very much for making this work, super grateful for your contribution 🥇

[rigor789]

Hi @koh110 - I think there is a small mistake in the workflow, the matrix defines node-version and in setup-node it's reading matrix.node - and I think all 3 builds use the default node version as a result.

axios/.github/workflows/ci.yml

Line 15 in f3ca637

node-version: [12.x, 14.x, 16.x]

axios/.github/workflows/ci.yml

Lines 19 to 22 in f3ca637

	- name: Setup node
	uses: actions/setup-node@v2
	with:
	node-version: ${{ matrix.node }}

[jasonsaayman]

@rigor789 could you put in a pull request to fix?

[rigor789]

@jasonsaayman sure, here it is #4069

[koh110]

@rigor789 @jasonsaayman Thank you for fixing my bug! I didn't notice it.