Upgrade GitHub Actions

[AdrianDsg]

Hi,
I just discovered this interesting project. I noticed that the GitHub Actions used in the CI workflows are outdated since a while.

Due to the use of the outdated Node.js version 12 some will break eventually.

I upgraded the GitHub Actions to the latest versions.

I also noticed that the GitHub host is harcoded in:

github-links/mdx_gh_links.py

Line 38 in 5bc28d3

URL_BASE = 'https://github.com'

Therefore usage on GitHub Enterprise Servers (GHES) is currently unfortunately not possible. Adding a new config item might fix it.

github-links/mdx_gh_links.py

Lines 119 to 120 in 5bc28d3

	'user': ['', 'GitHub user or organization.'],
	'repo': ['', 'Repository name.']

    'hostname': ['github.com', 'GitHub Enterprise Server hostname.']

The hostname would be parsed afterwards and used in URL_BASE.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

❗ No coverage uploaded for pull request base (master@5bc28d3). Click here to learn what that means.

Additional details and impacted files

@@            Coverage Diff             @@
##             master       #14   +/-   ##
==========================================
  Coverage          ?   100.00%           
==========================================
  Files             ?         2           
  Lines             ?       123           
  Branches          ?         0           
==========================================
  Hits              ?       123           
  Misses            ?         0           
  Partials          ?         0           

Flag	Coverage Δ
unittests	100.00% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[waylan]

Thank you for the update.

I also noticed that the GitHub host is harcoded in:

Therefore usage on GitHub Enterprise Servers* (GHES) is currently unfortunately not possible. Adding a new config item might fix.

Please feel free to submit a PR to address this. Or, if you are not able to do so, then please open a new issue so I don't forget about it.