-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Add a basic CI test checking that Emacs loads normally #1281
Labels
Comments
Merged
@bbatsov did you see the PR for this? No rush, just making sure. |
bbatsov
pushed a commit
that referenced
this issue
Apr 17, 2022
This addresses #1281. We just test whether Emacs will start with Prelude, which should uncover critical mistakes if any.
This can be closed, right? |
stefankeidel
pushed a commit
to stefankeidel/emacs-config
that referenced
this issue
Oct 4, 2022
This addresses bbatsov#1281. We just test whether Emacs will start with Prelude, which should uncover critical mistakes if any.
biern
pushed a commit
to biern/prelude
that referenced
this issue
Oct 16, 2022
This addresses bbatsov#1281. We just test whether Emacs will start with Prelude, which should uncover critical mistakes if any.
mklvr
pushed a commit
to mklvr/prelude
that referenced
this issue
Apr 11, 2023
This addresses bbatsov#1281. We just test whether Emacs will start with Prelude, which should uncover critical mistakes if any.
jmuhlich
pushed a commit
to jmuhlich/prelude
that referenced
this issue
May 23, 2023
This addresses bbatsov#1281. We just test whether Emacs will start with Prelude, which should uncover critical mistakes if any.
Bklyn
pushed a commit
to Bklyn/prelude
that referenced
this issue
Dec 30, 2023
This addresses bbatsov#1281. We just test whether Emacs will start with Prelude, which should uncover critical mistakes if any.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Such a test would be very useful on CI to prevent from silly mistakes like the one in #1279 creeping in. Basically we need to:
The text was updated successfully, but these errors were encountered: