Implement a nightly bump version automation workflow

[niketagrawal]

Create a GitHub action workflow that triggers nightly at a scheduled time and performs the following actions if there is a new commit(s) on the develop branch of tudat in the last 24 hours:

1. Bump the version number, create a tag, and push the tag and the bump version commit to the develop branch of the tudat repository
2. Bump the version number, create a tag, and push the tag and the bump version commit to the develop branch of the tudat repository

Currently, the above actions happen manually. When the develop branch of tudat is found to have reached a staged where a new version can be created, the tag and the version is created manually, and the version and tag is added on the tudat-feedstock repository, which then triggers the azure pipelines that creates the conda package.

[niketagrawal]

• [x] Test bump version locally in the clone of the fork.
• [x] Test pushing a tag with the version created above on the github repo
• [x] Put the above two commands in the ‘bump version’ and ‘push tag’ steps respectively in the github action workflow
• [x] Test the action in fork (without the dispatcher job)
• [x] Add the dispatcher job to send event to tudat-feedstock: Dispatch event didn't work on fork due to missing/incorrect token permissions. Opted to perform polling on feedstock repository for new commits on develop branch of tudat.
• [x] Test with adding the dispatcher job in the workflow

See workflow (in development) here: https://github.com/niketagrawal/tudat/blob/develop/.github/workflows/trigger_creation_new_dev_conda_pkg.yml

[niketagrawal]

Done

• GitHub actions workflow in tudat repository to bump the version in tudat repository when a new commit on dev branch is created
• GitHub actions workflow in tudat-feedstock that watches for new commits on dev branch of tudat and bumps version in meta.yml

Questions

• Con of polling on tudat-feedstock: Between subsequent poll intervals, multiple commits might be made on dev branch of tudat. How do bump the version number on feedstock in this case?
• At what point does the minor or patch version number needs to be updated? The bumpversion command in the workflow will need to be modified then, because by default it bumps the devxx number after the patch.

[niketagrawal]

The polling based workflow to detect new commits in tudat dev branch has the following cons:

• Each new commit on tudat will have to wait before the corresponding dev conda package is created
• Between two consecutive worklfow runs, dev branch of tudat could receive multiple commits.

To do

• [x] Revert the polling based workflow on tudat-feedstock to dispatch event based workflow so all commits on tudat are sure to trigger a new dev conda package.
• Create a separate bump version workflow in tudat that will bump the minor version on main when a new commit is made.
  • It is greed that bump version operation on master will stay as a manual operation.

[niketagrawal]

This GitHub Actions workflow will require personal access token to bump version, create a tag, and push the tag to tudat-feedstock repository. Below are the steps to create a personal access token to use in a Github action:

1. Go to Github profile -> settings > Developer settings (bottom of the menu on the left corner) > Personal access tokens > tokens (classic).
2. Generate new token -> tokens classic. Create a new token by adding a description, for example, 'nightly bump version workflow'

This token must now be specified to use in the tudat repository.

1. Got to tudat repository -> settings > secrets and variables > actions > new repository secret
2. Name the secret for example, bump_version_nightly. Go to the personal access token created in previous step and copy the token code and paste it as the value of this secret.
3. Mention this secret name in the bump version github action workflow.