Generate CHANGELOG from PRs labeled with changelog

[asimpson]

The goal of this config is to minimize discussion/decisions on what to include in the CHANGELOG when cutting a new release by moving the decision point to PR creation via the changelog label instead of release creation.

New Flow

1. Mark PRs for inclusion in the CHANGELOG as they are created by tagging the PRs with the label changelog.
2. When it comes time to cut a release use the generate release notes feature to generate the list of PRs to include in the CHANGELOG and then copy and paste them into the CHANGELOG.
3. PR the changes to the CHANGELOG along with the new version.
4. Once the PR is merged and the Drone build is passing go into Drone and "Promote the build" to release the new version.

[github-actions]

Backend code coverage report for PR #510
No changes

[github-actions]

Frontend code coverage report for PR #510
No changes

[aangelisc]

Nice work here 😊 I'd suggest we exclude PRs authored by dependabot from the CHANGELOG to avoid it getting messy, wdyt?

[andresmgot]

Sounds good! Can you add the updated instructions to the CONTRIBUTING file?

[andresmgot]

I'd suggest we exclude PRs authored by dependabot from the CHANGELOG to avoid it getting messy, wdyt?

as far as I understood, those PR won't have the label: changelog so they won't be added to the final changelog, right?

[aangelisc]

I'd suggest we exclude PRs authored by dependabot from the CHANGELOG to avoid it getting messy, wdyt?

as far as I understood, those PR won't have the label: changelog so they won't be added to the final changelog, right?

That's correct my bad, I misunderstood 🙃

[asimpson]

@andresmgot @aangelisc yep, this excludes everything unless it has the label.

[asimpson]

Sounds good! Can you add the updated instructions to the CONTRIBUTING file?

For sure, forgot we had one 😂

[andresmgot]

👍 thanks!