aboutsummaryrefslogtreecommitdiff
path: root/.github/workflows
AgeCommit message (Collapse)Author
2026-03-16ci: Reduce permissions and add zizmor settingJonas Bernoulli
2025-11-13Publish manual and statistics using webdavJonas Bernoulli
Re magit/magit#5472.
2024-11-21ci: Generate statistics weeklyJonas Bernoulli
2024-08-15ci: Publish manual for tagged releasesJonas Bernoulli
2024-06-25Remove magit-libgit.elJonas Bernoulli
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.
2023-01-17ci: Use new reusable test workflowJonas Bernoulli
2023-01-16ci: Add compile workflowJonas Bernoulli
2023-01-16ci: Use new reusable workflowsJonas Bernoulli
2023-01-06ci: Tell actions/checkout to not persist-credentialsJonas Bernoulli
It seems this should be the default as suggested at https://github.com/actions/checkout/pull/946.
2023-01-06ci: Give test workflow none of the optional permissionsJonas Bernoulli
See https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs.
2023-01-06Bump actions/checkout to version 3.dependabot[bot]
Bumps actions/checkout (https://github.com/actions/checkout) from version 2 to 3.
2023-01-05Use new compat-call macroJonas Bernoulli
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.
2022-08-21ci: Clone compat from Emacsmirror againKyle Meyer
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
2022-08-20ci: Clone compat from phikal/compat.elKyle Meyer
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
2022-05-13ci: Test on Emacs 28.1Jonas Bernoulli
2022-04-23ci: Build compatJonas Bernoulli
2022-04-23ci: Clone compat from emacsmirrorJonas Bernoulli
2022-04-23ci: Clone compatJonas Bernoulli
2022-03-07Automatically publish statisticsJonas Bernoulli
2022-01-30Add CI workflow to generate and distribute manualJonas Bernoulli
2021-11-08Fix CI by relying less on NixJonas Bernoulli
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.
2021-07-31ci: Suspend libgit testingJonas Bernoulli
2021-05-21Consolidate git/libgit CI stepsAshlynn Anderson
Seems unnecessary to have two separate steps here.
2021-04-28Run tests using both Git and libgit functions in CISam Cedarbaum
- 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.
2021-04-28Install Emacs with libegit in CISam Cedarbaum
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.
2021-01-24Replace Travis CI with GitHub ActionsVladimir Panteleev
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