Add changelog to docs

[tsalo]

Summary

Currently, the only changelog NiMARE has is the release notes. While those notes are useful and comprehensive, most users will not know to check them. I would like to see if we can come up with a way to generate the changelog automatically, whether after each release or after each PR.

Next steps

1. Look into GitHub Actions for changelog generation.
2. Add changelog file to docs folder.
3. Add changelog file to index.rst.

[tsalo]

@JulioAPeraza It looks like the new action wasn't triggered by the 0.0.12rc3 release.

[JulioAPeraza]

It looks like 0.0.12rc3 was a prereleased, so we will need to add prereleased to the activity type.

[JulioAPeraza]

It should look like this:

name: "Update Changelog"

on:
  release:
    types: [released, prereleased]

[tsalo]

Ohhh.... thanks! Do you want to open a PR with the fix?

[JulioAPeraza]

Sure!

[tsalo]

It failed: https://github.com/neurostuff/NiMARE/runs/6691490386?check_suite_focus=true

[JulioAPeraza]

I think it is an issue with the tag name of the release. I will open a PR with the fix.

[tsalo]

Hm... still failing: https://github.com/neurostuff/NiMARE/runs/6693393054?check_suite_focus=true

[JulioAPeraza]

Is the main branch protected against automatic commits by a GitHub Action?

[tsalo]

The status checks have to pass before PRs can be merged into main. I don't know if there's a way to treat GitHub Actions as special cases.

[JulioAPeraza]

https://github.com/stefanzweifel/git-auto-commit-action#push-to-protected-branches

[JulioAPeraza]

I think using a Personal Access Token (PAT) may fix this issue, as pointed out in the git-auto-commit-action repo. This has to be created and stored by you as the admin of the repo, right? After that, we can add:

- uses: actions/checkout@v2
  with:
    token: ${{ secrets.PAT }}

[tsalo]

Everything's looking good now (as of 0.0.12rc7), so I'm going to close this.