How to work with issues and files created through the provider?

[mattias-fjellstrom]

I have a general question about two resources: github_repository_file and github_issue (and there are possibly more resources that have the same issue).

I thought about creating a module for setting up new repositories. Apart from configuring each repository in a given way, I also want each repository to have a few common files and some "starter issues".
However, once a team starts working with the repo they might make changes to these files, and they will work with and resolve the issues. But the next time I run a terraform apply I will reset the changes they have made.

My question is, how are these resources supposed to be used? I could run a single apply and then remove them from my state and from my configuration, but that is a lot of manual work. I also understand that it wouldn't really make sense for Terraform to ignore the changes made to the files. It just feels like these resources really shouldn't be part of the provider. Could anyone enlighten me here?

[mattias-fjellstrom]

Same thing for github_actions_secret (and other secrets). I think it makes sense to add a few placeholder secrets to a repo during initial setup, but if subsequent terraform apply's overwrite the values it doesn't sound like a good idea anymore.