Hi everyone,

as you probably have already seen, there are a few new status badges in the 
trac ticket display.
We have now:
1. Linter that checks that the code of the current branch adheres to the 
style guidelines. In order to see details when it fails, you can click on 
it and then select the most recent workflow run. (This already exists for a 
while)
2. Buid & test that builds sage for the current branch (incrementally on 
top of the system packages of the develop branch) and runs the test. 
Details are again available by clicking on the badge. (This is currently 
still gray until https://trac.sagemath.org/ticket/33263 is merged into 
master)
3. Build documentation workflow that builds the documentation for the 
current branch. If you click on it, you get the html output of the 
successful run. The idea is to use this to easily inspect changes to the 
documentation without the need to locally rebuild the docs yourself. If the 
doc build fails, you can go to 
https://github.com/sagemath/sagetrac-mirror/actions/workflows/doc-build.yml 
and choose the particular branch to see what went wrong.
4. Open in gitpod. This will spin up a pre-configured dev environment in 
the browser (based on VS code), where the branch is already checked-out and 
everything is pre-build. Feel free to use it to quickly check that the 
changes in the ticket work as expected or to even make further changes 
yourself. To find out more: https://www.gitpod.io/

The idea is that these three status badges complement the existing 
patchbots (and maybe even replace them in the future). In particular, they 
are supposed to always be green. Please keep this in mind when reviewing a 
ticket. 

-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-devel/6fa086b9-276e-419e-9232-ff03f2b0708cn%40googlegroups.com.

Reply via email to