git phorge sounds right, amend / land as real verbs is exactly the mental model the docs are struggling to explain, and no PHP dependency removes the first thing I got stuck on. Curious what the September test with the 5 says.

I confirm the workflow works well.

The workflow itself has never really been the problem. It's fine, and it maps closely enough to a GitHub PR loop. What's heavy I would say is how much arrives at once on the first contributions, it's equal to too much current for a wire.

GPT-5.6-Sol proposal: https://chatgpt.com/share/6a8a838d-4cbc-83eb-b59e-5d847a64b03e

This is important, as on WindRiver and my local workstation, the PHP installations miss some of the database drivers (SQLite, MongoDB, old MySQL from before PHP 8).

It could be solved upstream with 3006.26.

Current status: this is mostly implemented, but still to document properly per previous comment.

Not a priority right now, as we use Alkane to trigger website deployments.

In a Debian container, this works:

Done, GitHub shows 9d5c84e52ed2 too for main and doesn't have a master branch anymore.

For the last one, rDII, we currently have:

We don't currently have problem deploying from the staging area, even if, especially with Alkane, there is less use of this.

Vault is now alive and used for credentials provisioned by Salt.

Alkane doesn't need any new account. We can send a request to an URL and it will be run by the deploy user.

Documentation to add:

• How to create a new component
  • make
  • use last version of dependencies like OmniTools
  • git remote
  • yes, we can directly use ./_utils/repo/export-commits-to-manyrepos.sh but we need to do git push yaml yaml:mainkk
• How to push tags easily

Well, FANTOIR isn't the format used by French administrations anymore. The TOPO database is now used.

Some of the plugins from the template can still be used as documented on https://www.jenkins.io/solutions/php/: