donkirkby / donkirkby/live-py-plugin
Test Emacs version on GitHub Actions
- Dominant language
- Python
- Stars
- 302
- Forks
- 63
- Avg merge
- 6h 50m
- Merged PRs (30d)
- 2
Description
## What I did
Added the Emacs ERT tests to the GitHub Actions workflow, after TravisCI stopped working.
## What happened
It complained with this error:
```
emacs: standard input is not a tty
```
## What I wanted to happen
Run the way it used to on Travis.
## Analysis
I found a bunch of actions to help:
* [setup emacs](https://github.com/marketplace/actions/set-up-emacs)
* [emacs lisp check](https://github.com/marketplace/actions/emacs-lisp-check) I haven't tried it yet, but it looks like it can run ERT.
* [cask](https://github.com/cask/cask) I used it on Travis, but I think it's not needed with setup emacs.
* There's some discussion on actions/runner#241. That's where I learned about `script` and `scriptreplay`.
Contributor guide
Research direction
Start by reading the GitHub Actions workflow and the existing TravisCI setup for the Emacs ERT tests. Reproduce the `emacs: standard input is not a tty` failure, then confirm that the workflow runs the ERT tests successfully without requiring a terminal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- emacs, github-actions
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100