2.0.0

Version 2 🎉 ✨

For a long time, this workflow was using a dummy commit approach to keep the repositories active, this method was effective but came with a side effect. It automatically creates a dummy commit every 50 days, which makes this workflow un-usable for many serious open-source projects, since they heavily rely on commit history. To keep the repository active, this was the only option when I created this workflow.

GitHub made some changes recently, now simply calling the GitHub Action API's enable API Call will keep the workflow active indefinitely. This feature was added to this workflow as an opt-in feature for people to use. Version 2 will make this method the default method for the keep-alive workflow.

People who are using v1 and master tags of this workflow will continue using the dummy commit method since the newly added API-based method requires explicit permission for the API Keys for it to function.

Migrating from v1 to v2

If you are an existing user which used this workflow's v1 version, you can easily migrate to v2 by simply updating the permissions key in your workflow:

Change:

permissions:
  contents: write

to

permissions:
  actions: write

And change the workflow's version from gautamkrishnar/keepalive-workflow@v1 or gautamkrishnar/keepalive-workflow@master to gautamkrishnar/keepalive-workflow@v2. This will automatically start using the workflow's API based method. No more dummy commits 🕺 .

What's Changed

• Updated the workflow to v2 to make use of API keepalive method by default instead of dummy commit based method

Full Changelog: v1...2.0.0