chore: added header checker

kikoso commented 10 months ago

This PR adds a new GitHub flow to check whether our files contain a copyright header.

Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[X] Make sure to open a GitHub issue as a bug/feature request before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
[X] Edit the title of this pull request with a semantic commit prefix (e.g. "fix: "), which is necessary for automated release workflows to decide whether to generate a new release and what type it should be.
[ ] Will this cause breaking changes to existing Java or Kotlin integrations? If so, ensure the commit has a BREAKING CHANGE footer so when this change is integrated a major version update is triggered. See: https://www.conventionalcommits.org/en/v1.0.0/
[X] Ensure the tests and linter pass
[X] Code coverage does not decrease (if any source code was changed)
[X] Appropriate docs were updated (if necessary)

Fixes #1284 🦕

wangela commented 10 months ago

Should we add .gradle files too?

kikoso commented 10 months ago

Should we add .gradle files too?

~~We generally do not add them in other repos~~t, and generally they do not contain any relevant code besides the build support. Unless there is a non-technical reason we could leave them out.

Update. We do have a mixed approach here, with some repos like android-maps-utils adding headers, and compose not. I would still go for checking the header of what can be susceptible to falling under a copyright issue. Arguable, build files should not be a part of this.

wangela commented 10 months ago

This should be merged as a chore:

googlemaps-bot commented 4 months ago

Code Coverage

There is no coverage information present for the Files changed

Total Project Coverage	38.15%	:green_apple:

googlemaps / android-maps-utils

chore: added header checker #1285

Code Coverage