Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI: migrate from Travis to GitHub Actions #389

Closed
wants to merge 11 commits into from

Conversation

davidhcefx
Copy link
Contributor

@davidhcefx davidhcefx commented Mar 7, 2022

It seems that PRs later than 28 May 2021 all failed CI, plus the fact that Travis CI's free trial account has a limited quota, I think it's reasonable for us to switch to Github Actions for performing shellcheck.
Aside from that, I added a new test highlight_test to check for syntax errors in all of the rcfiles, using latest GNU nano.

image

- Removed .travis.yml and shellcheck.sh
- Added CI badge to README
@davidhcefx davidhcefx force-pushed the master branch 4 times, most recently from ba6ae3c to 99ee3f4 Compare March 8, 2022 00:42
- Lots of syntax regex are poorly written and did not ends with a '$',
   which caused them competing with other regex rules.
- Basing on highlight.js, I enhanced the highlighting rules in various aspects.
- See also: scopatz#358
- Improve colorings based on iPython (colors=Linux):
    - Green for exceptions and function names.
    - Red for keywords such as `from` and `not`.
    - Cyan for keywords such as `for` and `if`.
- Fix empty strings not correctly highlighted.
- Fix block comments not correctly highlighted when nothing follows `===`.
- Add support for "TODO".
- [Batch] Fix that using "::" as comments sometimes failed
- [html] Tabs give 2 spaces by default
- [JS] Tabs give 2 spaces by default; Allow comments to be inline with code.
- [Sh] Also highlight PKGBUILD; Fix `${v%tail}` not highlighted; Use shellcheck as linter
- Full list of directives updated from: http://nginx.org/en/docs/dirindex.html
- Deleted 3 keywords, added 233 keywords
- New error message "Standard input is not a terminal" should be ignored.
- nano changed its behavior to produce error messages AFTER program exited.
@davidhcefx
Copy link
Contributor Author

Closed in favor of #421

@davidhcefx davidhcefx closed this Feb 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant