Patch 2113 add CI support using github actions

Title add CI support using github actions
Superseder Nosy List bf
Related Issues
Status accepted Assigned To

Created on 2020-11-14.17:02:28 by bf, last changed 2020-12-19.21:44:19 by ganesh.

File name Status Uploaded Type Edit Remove
add-ci-support-using-github-actions.dpatch bf, 2020-11-14.17:02:27 application/x-darcs-patch
patch-preview.txt bf, 2020-11-14.17:02:27 text/x-darcs-patch
unnamed bf, 2020-11-14.17:02:27 text/plain
See mailing list archives for discussion on individual patches.
msg22508 (view) Author: bf Date: 2020-11-14.17:02:27
1 patch for repository http://darcs.net/screened:

patch e35f50943146937cf8f9dcfb30a6d02604ed83b9
Author: Ben Franksen <ben.franksen@online.de>
Date:   Sat Nov 14 18:07:32 CET 2020
  * add CI support using github actions
  For the moment this is manually triggered using ./release/trigger-ci. This
  script takes the basename of the current directory as the git branch name,
  makes sure we are inside a darcs repo, and then creates an automatic commit
  on that branch (creating it if necessary), then force-pushes that branch to
  the github repo, which will trigger the CI run. If a .git does not exist
  yet, it will be created, which means your branch will be reset to this
  snapshot as the first and only version. The configuration of the job to run
  is in .github/workflows/build-and-test.yml. Windows tests are currently
  disable because they run into errors I have no idea how to fix.
msg22556 (view) Author: ganesh Date: 2020-12-19.20:23:29
Looks good
Date User Action Args
2020-11-14 17:02:28bfcreate
2020-11-14 17:03:06bfsetstatus: needs-screening -> needs-review
2020-12-19 20:23:29ganeshsetstatus: needs-review -> accepted-pending-tests
messages: + msg22556
2020-12-19 21:44:19ganeshsetstatus: accepted-pending-tests -> accepted