| Age | Commit message (Collapse) | Author |
|
This is displayed in a plaintext textarea.
|
|
|
|
|
|
|
|
Also fix link to support category and tweak link to manual.
|
|
|
|
|
|
Re magit/magit#5472.
|
|
Closes #5429.
|
|
|
|
|
|
|
|
|
|
After not doing anything for years, it suddenly began trying to run,
which failed because it is not one of the actions I have allowed for
this organization. That didn't keep it from trying two dozen times
over the course of two weeks. Good riddance.
I'm actually already keeping my action dependencies up-to-date, so I
don't need this.
|
|
|
|
|
|
|
|
This is just a proof-of-concept. Until that changes its dead weight
that should not be packaged. Removing it from version control is the
only way to prevent it from getting packaged anyway.
|
|
|
|
|
|
|
|
|
|
It seems this should be the default as suggested
at https://github.com/actions/checkout/pull/946.
|
|
See https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs.
|
|
Bumps actions/checkout (https://github.com/actions/checkout)
from version 2 to 3.
|
|
Documentation at https://docs.github.com/en/code-security/dependabot/working-with-dependabot/automating-dependabot-with-github-actions.
|
|
Bump version/snapshot to make sure we get a Compat version
that includes the new macro. This had to be done manually
as the bump-snapshots make target suffers from bit rot.
Closes #4836.
|
|
This reverts commit 5e1e6d31 (ci: Clone compat from phikal/compat.el,
2022-08-20). emacsmirror/compat is now up to date:
https://github.com/magit/magit/commit/5e1e6d317b2ea27e734b73be6f1904f7578267fd#commitcomment-81753297
|
|
The test builds are consistently failing in the "Build magit" phase
with
In toplevel form:
git-commit.el:127:1:Error: Symbol’s function definition is void: and-let*
github.com/emacsmirror/compat (b416a89, 2022-07-20) is about a month
behind git.sr.ht/~pkal/compat, and updating to compat's 99e7939
(2022-08-13) resolves the build failures [*].
At least until emacsmirror/compat catches up, point to the GitHub
mirror at phikal/compat.el, which is up to date with
git.sr.ht/~pkal/compat.
[*] https://github.com/magit/magit/actions/runs/2895438505
|
|
|
|
|
|
|
|
|
|
Favor links over duplicating information and then letting it get
out-of-date. Of course links may break too, so fix those too.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The previous implementation kept breaking and we got no help fixing
that. More or less go back to the previous implementation, which we
know how to keep running without any outside help.
Previously testing using libgit was disabled because it was broken,
while now there simply isn't any code to attempt to test that.
|
|
I have stopped answering questions on that platform a few months ago
and nobody else took over, so many questions remain unanswered. Also
it is being moderated by people who have some rigid ideas of what does
and does not constituted an acceptable answer, and I am not interested
in wasting time on making those people happy.
|
|
|
|
Seems unnecessary to have two separate steps here.
|
|
- Add new make targets `test-git' and `test-libgit', which ensure
that tests are run using the Git CLI and libgit, respectively.
- Add `git_impl' dimension to GitHub Actions build matrix, which
controls which Git implementation that tests use.
|
|
Replace the `setup-emacs' GitHub action with a custom Nix install
(defined in t/default.nix) that bundles Emacsen with libegit and
its other dependencies.
|
|
npostavs/emacs-travis is replaced with the purcell/setup-emacs action.
The host operating system version is bumped from Ubuntu Xenial (16.04)
to Bionic (20.04), as 16.04's curl doesn't have --retry-connrefused,
which is needed by purcell/setup-emacs.
Notification settings are configured per-user in their GitHub settings:
https://docs.github.com/en/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#github-actions-notification-options
|
|
|
|
|