feat: add branch_protection resource #72

❯ terraform validate examples/ ╷ │ Warning: Provider development overrides are in effect │ │ The following provider development overrides are set in the CLI configuration: │ - go-gitea/gitea in /home/v3nc/Documents/git/gitea.com/gitea/terraform-provider-gitea │ │ The behavior may therefore not match any released version of the provider and applying changes may cause the state to become incompatible with published releases. ╵ ╷ │ Error: Unsupported argument │ │ on examples/main.tf line 57, in resource "gitea_team" "test_team": │ 57: members = [gitea_user.test.username] │ │ An argument named "members" is not expected here. ╵ ╷ │ Error: Unsupported argument │ │ on examples/main.tf line 65, in resource "gitea_team" "admin_team": │ 65: members = [data.gitea_user.me.username] │ │ An argument named "members" is not expected here. ╵ ╷ │ Error: Missing required argument │ │ on examples/main.tf line 99, in resource "gitea_token" "test_token": │ 99: resource "gitea_token" "test_token" { │ │ The argument "scopes" is required, but no definition was found. ╵ ╷ │ Error: Unsupported argument │ │ on examples/main.tf line 100, in resource "gitea_token" "test_token": │ 100: username = data.gitea_user.me.username │ │ An argument named "username" is not expected here. ╵ 

In my opionion the `terraform validate` should check the syntax of the examples. By running without any directory specified, it runs in the root dir, where no tf code is found and complains about my tests, because the `-test-directory` defaults to `tests`. ``` ❯ terraform validate examples/ ╷ │ Warning: Provider development overrides are in effect │ │ The following provider development overrides are set in the CLI configuration: │ - go-gitea/gitea in /home/v3nc/Documents/git/gitea.com/gitea/terraform-provider-gitea │ │ The behavior may therefore not match any released version of the provider and applying changes may cause the state to become incompatible with published releases. ╵ ╷ │ Error: Unsupported argument │ │ on examples/main.tf line 57, in resource "gitea_team" "test_team": │ 57: members = [gitea_user.test.username] │ │ An argument named "members" is not expected here. ╵ ╷ │ Error: Unsupported argument │ │ on examples/main.tf line 65, in resource "gitea_team" "admin_team": │ 65: members = [data.gitea_user.me.username] │ │ An argument named "members" is not expected here. ╵ ╷ │ Error: Missing required argument │ │ on examples/main.tf line 99, in resource "gitea_token" "test_token": │ 99: resource "gitea_token" "test_token" { │ │ The argument "scopes" is required, but no definition was found. ╵ ╷ │ Error: Unsupported argument │ │ on examples/main.tf line 100, in resource "gitea_token" "test_token": │ 100: username = data.gitea_user.me.username │ │ An argument named "username" is not expected here. ╵ ``` That reveals that there are some bugs in the examples at the moment. I will update the examples and point the `tf validate` to the examples dir in the pipeline.

The `terraform validate` uses the released version of the provider not the code from the pr. I`m not sure about the purpose of this pipeline, it will never validate the example code before the new version is published published. It will fail after releasing with not up to date examples or it will fail before the release with updated examples which are (mayby) not supported by the current provider version. I would suggest to build the provider from the pr with development override enabled and test the example for the current commit. The validate does not work recursive, so only the `./examples/main.tf` is tested, the more useful examples in the `./examples/resources` directory will still not be validated.