Conversation
ee1197a to
4f0fa1d
Compare
4f0fa1d to
75c0a2a
Compare
Expand paths-ignore in main, integration, and deployment workflows to cover all Markdown files, the docs directory, and mkdocs.yml. This avoids running expensive integration tests when only documentation is modified.
docs/dev/how-to/make-a-release.md
Outdated
| git push upstream HEAD:main | ||
| ``` | ||
|
|
||
| - TODO: update the release notes manually |
There was a problem hiding this comment.
Is that for another PR? Shall I create an issue for that?
|
|
||
| ## diracx release | ||
|
|
||
| Releases are managed by `ReleasePlease`. The token used to perform it belongs to `diracbot` github user |
There was a problem hiding this comment.
Shall we document diracx-web release here? I think yes.
It would be very similar to diracx release.
The only differences are:
- we are not using
diracbotbecause we don't need it (at least for now) pypi releasebecomesnpm releasefordiracx-web-components. See https://www.npmjs.com/package/@dirac-grid/diracx-web-components
There was a problem hiding this comment.
Isn't it "DIRACGridBot" instead of "diracbot"?
There was a problem hiding this comment.
Can you please push directly to this branch @aldbr ?
There was a problem hiding this comment.
I prepared DIRACGrid/diracx-web#484 to align the DiracX-Web release process with the DiracX one. Ideally it needs #527 and another PR that will follow.
Once reviewed and merged, I'll add the diracx-web release process here.
|
|
||
| ## diracx release | ||
|
|
||
| Releases are managed by `ReleasePlease`. The token used to perform it belongs to `diracbot` github user |
There was a problem hiding this comment.
Isn't it "DIRACGridBot" instead of "diracbot"?
docs/dev/how-to/make-a-release.md
Outdated
|
|
||
| - TODO: update the release notes manually | ||
|
|
||
| 4. Merge the PR |
There was a problem hiding this comment.
| 4. Merge the PR | |
| 4. Merge the `release-please` PR |
docs/dev/how-to/make-a-release.md
Outdated
|
|
||
| # How to make a new DiracX release | ||
|
|
||
| 1. Merge any PR you want in your release |
There was a problem hiding this comment.
Remove this step, it's done asynchronously.
No description provided.