Protect-secrets-on-pr

[mauwii]

• in this way the action is used from the base repository
• also use new secret HUGGINGFACE_TOKEN (username:token)
  • f.e. noreply@github.com:hf_lkaugfklagwrjglaslzfgkjzzf
• change pr prompt file to validate_pr_prompt.txt

@lstein: you need to create the new secret as mentioned above

[mauwii]

@lstein to add the secret, while in the repository, click on:

1. settings
2. secrets
3. actions
4. New Repository Secret
5. name it HUGGINGFACE_TOKEN with content of username:huggingface_token
   (for me mauwii@provider.de:hf_blablabla)

[lstein]

I've done this using my HuggingFace account and access token. Should I remove the SD URL as well?

[mauwii]

I've done this using my HuggingFace account and access token. Should I remove the SD URL as well?

since secrets.SD_V1_4_URL shouldn't be reffered from the actions anymore it should be safe to remove it 👍🏻

[mauwii]

@lstein only name:token as the secret, no line break in the end!

This is because there is a line break in the end of the secret: https://github.com/invoke-ai/InvokeAI/actions/runs/3347426747/jobs/5545396133#step:9:5

This is how it looks without the line break: https://github.com/mauwii/stable-diffusion/actions/runs/3347402241/jobs/5545344701#step:9:5