Utility scripts

[dataclouder]

Add .changes folder

Add a folder .changes' and scripts/make-changelog.shto avoidCHANGELOGconfilcts . This is similar to the organization of terraform-provider-vcd. To re-assemble the CHANGELOG, use./scripts-make-changelog.sh VERSION`.

To show how the CHANGELOG would be organized, I added the items for v2.12.0 and v2.12.1.

Allow staticcheck to run in GitHub Actions

The test with staticcheck had stopped working when we transitioned from Travis to GitHub Actions. Changing the trigger variable fixed it. I also added a skip comment for a function that is used on demand for debugging.

[lvirbalas]

What are the main differences from the way we generate changelog in Terraform?
BTW, there are typos in the PR description: "terraform-prov0wider-vcd. To re-assemple"

[dataclouder]

What are the main differences from the way we generate changelog in Terraform?
BTW, there are typos in the PR description: "terraform-prov0wider-vcd. To re-assemple"

The main differences:

• We use a single block CHANGELOG.md that causes conflicts at almost every merge
• In terraform-provider-vcd we use headers for all items in the CHANGELOG, while in go-vcloud-director we only use "breaking changes" and improvements.

This PR aims at having both CHANGELOGs follow the same pattern.
If you run ./scripts-make-changelog.sh v2.12.0 you'd see how the new format applies to the latest release. Note: the outcome has extra spacing to allow for better editing of the final CHANGELOG.

[lvirbalas]

LGTM!

Only one thing: I see in the generated CHANGELOG extra new lines in between the groups of changes. Is the idea to reconcile them manually before the release? This could be human-error-prone.

[dataclouder]

I see in the generated CHANGELOG extra new lines in between the groups of changes. Is the idea to reconcile them manually before the release? This could be human-error-prone.

We can make a "perfect and final" assembly tool, but it would require using something better than a shell script. The goal here is to make a good-enough draft that we can adapt manually before releasing. We have been doing the same in terraform-provider-vcd.

[Didainius]

Thanks! A brief test worked.