From 4ea7e50334b32fd445ce85956619ebe1b5fb29f4 Mon Sep 17 00:00:00 2001 From: Lauren Clisby Date: Mon, 4 Nov 2024 17:24:56 +0100 Subject: [PATCH] Fix 91-developer.md (#922) --- docs/src/91-developer.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/src/91-developer.md b/docs/src/91-developer.md index ee0e7b70..2963be0a 100644 --- a/docs/src/91-developer.md +++ b/docs/src/91-developer.md @@ -441,30 +441,30 @@ See the file for an example of profiling code. When publishing a new version of the model to the Julia Registry, follow this procedure: > **Note:** -> To be able to register, you need to be a member of the organisation TulipaEnergy and have your visibility set to public: +> To be able to register, you need to be a member of the organisation TulipaEnergy and have your visibility set to public:
> ![Screenshot of public members of TulipaEnergy on GitHub](./images/PublicMember.png) 1. Click on the `Project.toml` file on GitHub. -2. Edit the file and change the version number according to [semantic versioning](https://semver.org/): Major.Minor.Patch +1. Edit the file and change the version number according to [semantic versioning](https://semver.org/): Major.Minor.Patch
![Screenshot of editing Project.toml on GitHub](./images/UpdateVersion.png) -3. Commit the changes in a new branch and open a pull request. Change the commit message according to the version number. +1. Commit the changes in a new branch and open a pull request. Change the commit message according to the version number.
![Screenshot of PR with commit message "Release 0.6.1"](./images/CommitMessage.png) -4. Create the pull request and squash & merge it after the review and testing process. Delete the branch after the squash and merge. +1. Create the pull request and squash & merge it after the review and testing process. Delete the branch after the squash and merge.
![Screenshot of full PR template on GitHub](./images/PullRequest.png) -5. Go to the main page of repo and click in the commit. +1. Go to the main page of repo and click in the commit.
![Screenshot of how to access commit on GitHub](./images/AccessCommit.png) -6. Add the following comment to the commit: `@JuliaRegistrator register` +1. Add the following comment to the commit: `@JuliaRegistrator register`
![Screenshot of calling JuliaRegistrator in commit comments](./images/JuliaRegistrator.png) -7. The bot should start the registration process. +1. The bot should start the registration process.
![Screenshot of JuliaRegistrator bot message](./images/BotProcess.png) -8. After approval, the bot will take care of the PR at the Julia Registry and automatically create the release for the new version. +1. After approval, the bot will take care of the PR at the Julia Registry and automatically create the release for the new version.
![Screenshot of new version on registry](./images/NewRelease.png) Thank you for helping make frequent releases!