Searched hist:"290 ea73da0bf2b8df7bddcb78a7c73c52929c96c" (Results 1 – 6 of 6) sorted by relevance
| /dokuwiki/ |
| H A D | .editorconfig | 290ea73da0bf2b8df7bddcb78a7c73c52929c96c Thu Feb 23 14:03:01 UTC 2023 Andreas Gohr <andi@splitbrain.org> Automate the release workflow using GitHub actions
This introduces a two-part release mechanism. A manually triggered
workflow asks for the important info like type of release (stable, rc)
and code name. It then creates a cleanly mergable pull request.
When that pull request is merged, a release is automatically tagged,
built and uploaded.
Another workflow is introduced to keep track of the deleted.files info.
This is one less chore to do on a release.
A new scheme for tags is also introduced, making all tags sortable,
regardless of their type. They follow the pattern
release-YYYY-MM-DD(<hotfixletter>|rc)
A script will be used to clean-up the existing tags.
|
| H A D | .gitattributes | 290ea73da0bf2b8df7bddcb78a7c73c52929c96c Thu Feb 23 14:03:01 UTC 2023 Andreas Gohr <andi@splitbrain.org> Automate the release workflow using GitHub actions
This introduces a two-part release mechanism. A manually triggered
workflow asks for the important info like type of release (stable, rc)
and code name. It then creates a cleanly mergable pull request.
When that pull request is merged, a release is automatically tagged,
built and uploaded.
Another workflow is introduced to keep track of the deleted.files info.
This is one less chore to do on a release.
A new scheme for tags is also introduced, making all tags sortable,
regardless of their type. They follow the pattern
release-YYYY-MM-DD(<hotfixletter>|rc)
A script will be used to clean-up the existing tags.
|
| /dokuwiki/.github/workflows/ |
| H A D | release-preparation.yml | 290ea73da0bf2b8df7bddcb78a7c73c52929c96c Thu Feb 23 14:03:01 UTC 2023 Andreas Gohr <andi@splitbrain.org> Automate the release workflow using GitHub actions
This introduces a two-part release mechanism. A manually triggered
workflow asks for the important info like type of release (stable, rc)
and code name. It then creates a cleanly mergable pull request.
When that pull request is merged, a release is automatically tagged,
built and uploaded.
Another workflow is introduced to keep track of the deleted.files info.
This is one less chore to do on a release.
A new scheme for tags is also introduced, making all tags sortable,
regardless of their type. They follow the pattern
release-YYYY-MM-DD(<hotfixletter>|rc)
A script will be used to clean-up the existing tags.
|
| H A D | release-build.yml | 290ea73da0bf2b8df7bddcb78a7c73c52929c96c Thu Feb 23 14:03:01 UTC 2023 Andreas Gohr <andi@splitbrain.org> Automate the release workflow using GitHub actions
This introduces a two-part release mechanism. A manually triggered
workflow asks for the important info like type of release (stable, rc)
and code name. It then creates a cleanly mergable pull request.
When that pull request is merged, a release is automatically tagged,
built and uploaded.
Another workflow is introduced to keep track of the deleted.files info.
This is one less chore to do on a release.
A new scheme for tags is also introduced, making all tags sortable,
regardless of their type. They follow the pattern
release-YYYY-MM-DD(<hotfixletter>|rc)
A script will be used to clean-up the existing tags.
|
| H A D | deletedFiles.yml | 290ea73da0bf2b8df7bddcb78a7c73c52929c96c Thu Feb 23 14:03:01 UTC 2023 Andreas Gohr <andi@splitbrain.org> Automate the release workflow using GitHub actions
This introduces a two-part release mechanism. A manually triggered
workflow asks for the important info like type of release (stable, rc)
and code name. It then creates a cleanly mergable pull request.
When that pull request is merged, a release is automatically tagged,
built and uploaded.
Another workflow is introduced to keep track of the deleted.files info.
This is one less chore to do on a release.
A new scheme for tags is also introduced, making all tags sortable,
regardless of their type. They follow the pattern
release-YYYY-MM-DD(<hotfixletter>|rc)
A script will be used to clean-up the existing tags.
|
| /dokuwiki/.github/ |
| H A D | release.php | 290ea73da0bf2b8df7bddcb78a7c73c52929c96c Thu Feb 23 14:03:01 UTC 2023 Andreas Gohr <andi@splitbrain.org> Automate the release workflow using GitHub actions
This introduces a two-part release mechanism. A manually triggered
workflow asks for the important info like type of release (stable, rc)
and code name. It then creates a cleanly mergable pull request.
When that pull request is merged, a release is automatically tagged,
built and uploaded.
Another workflow is introduced to keep track of the deleted.files info.
This is one less chore to do on a release.
A new scheme for tags is also introduced, making all tags sortable,
regardless of their type. They follow the pattern
release-YYYY-MM-DD(<hotfixletter>|rc)
A script will be used to clean-up the existing tags.
|