Trac: Link to Github actions results, in particular for linters

[mkoeppe]

Follow-up from #30404 (Add pyright and pycodestyle checks as Github actions):

What is left to do is to add the integration of the github action output to trac. That can be done as follows:

1. Sync trac branches to sagetrac-mirror (by post-commit hook)
2. Activate github actions in the sagetrac-mirror github repo
3. Add the following code to either the patchbot output or to the trac ticket header (next to the patchbot button)

<a href="https://github.com/sagemath/sagetrac-mirror/actions?query=workflow%3ALint+branch%3BRANCH"><img src="https://github.com/sagemath/sagetrac-mirror/workflows/Lint/badge.svg?branch=BRANCH&event=push"/></a>

Here BRANCH needs to be replaced by the branch.
Giving something similar to

As this requires rights to the github repo and trac config, I cannot do this and have to leave it to somebody else.

CC: @dimpase @fchapoton @embray

Component: website/wiki

Issue created by migration from https://trac.sagemath.org/ticket/30877

[fchapoton]

comment:1

see also sagemath/sage_trac_plugin#21

[tobiasdiez]

comment:2

Thanks @fchapoton for the pointer! Based on your code, I've added a badge for github as well: sagemath/sage_trac_plugin#22

@dimpase could you please extend the post-commit hook to push to include github as well. That would be awesome! Thanks.

[dimpase]

comment:3

Replying to @tobiasdiez:

Thanks @fchapoton for the pointer! Based on your code, I've added a badge for github as well: sagemath/sage_trac_plugin#22

@dimpase could you please extend the post-commit hook to push to include github as well. That would be awesome! Thanks.

I'm trying to re-create a mirror on github atm. Our repo apparently has too many branches for GH to take it in one go. So it has to go branch by branch, tag by tag...

[tobiasdiez]

comment:4

Replying to @dimpase:

I'm trying to re-create a mirror on github atm. Our repo apparently has too many branches for GH to take it in one go. So it has to go branch by branch, tag by tag...

Thanks a lot! It appears the initial sync was successful but it stopped pushing further updates to github about 8 days ago.

It would also be great if you could activate the github actions in the sagetrac mirror.

[dimpase]

comment:6

Replying to @tobiasdiez:

Replying to @dimpase:

I'm trying to re-create a mirror on github atm. Our repo apparently has too many branches for GH to take it in one go. So it has to go branch by branch, tag by tag...

Thanks a lot! It appears the initial sync was successful but it stopped pushing further updates to github about 8 days ago.

OK, I've finally got around to install the hook to actually do the mirror-pushing, it seems to work now.

It would also be great if you could activate the github actions in the sagetrac mirror.

All actions? I've done this for the time being, so it's active now, but perhaps we need to look into trimming the list.

[tobiasdiez]

comment:7

Nice! After #30404 and #30910, the only github actions that should run after a push are the linter tests (that only take a couple of min).

So, the only thing left is to review and merge sagemath/sage_trac_plugin#22, so I'll put this ticket on "ready-for-review" now.

[dimpase]

comment:8

I don't understand how sage_trac_plugin is supposed to be doing anything here.
There is something to be done on trac server, yes...

[tobiasdiez]

comment:9

To my understanding the sage_trac_plugin handles the sage-specific customization of trac. Isn't this the case?

[dimpase]

comment:10

Replying to @tobiasdiez:

To my understanding the sage_trac_plugin handles the sage-specific customization of trac. Isn't this the case?

sage_trac_plugin is a client (mostly a git extension, with various addons to
deal with trac tickets).

It does have a kind of GitLab integration (used by the release manager, I suppose),

• this integration does autoimatic opening/managing of trac tickets for MRs on GitLab.
  Anything added there would only affect trac tickets opened via GitLab, I guess.

I don't think there is a config for our trac server maintained as a git repo anywhere.
(At least I don't know).

[dimpase]

comment:11

GitHub's "select actions to allow" looks like

Allow specified actions
Enter a comma-separated list of actions

...

Wildcards, tags, and SHAs are allowed. Examples: monalisa/octocat@*, monalisa/octocat@v2, monalisa/*

Could you provide a list of actions to enable this way, in this format?

[dimpase]

comment:12

I'm stopping the actions for now, as now pushes to trac git trigger a full Actions testsuite.

[tobiasdiez]

comment:13

Replying to @dimpase:

GitHub's "select actions to allow" looks like
...
Could you provide a list of actions to enable this way, in this format?

To my knowledge, that's for specifying which actions are allowed in the workflows (i.e. as steps in the workflow, e.g. checkout), but not the workflows itself.
The trigger for the workflows are specified at the beginning of the workflow file.