Running core_install initiates wordpress and creates an admin user with a password. Per default the password is generated and printed to the logs. Passwords in the logs aren't a good idea, especially when running this inside a CI pipeline. Further there is no way to access the password other than copying it from the logs.
I decided to add a new secret, to generate and store the admin password. This would open a breaking change, because the new secret must be generated.
Running core_install initiates wordpress and creates an admin user with a password. Per default the password is generated and printed to the logs. Passwords in the logs aren't a good idea, especially when running this inside a CI pipeline. Further there is no way to access the password other than copying it from the logs.
I decided to add a new secret, to generate and store the admin password. This would open a breaking change, because the new secret must be generated.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Running core_install initiates wordpress and creates an admin user with a password. Per default the password is generated and printed to the logs. Passwords in the logs aren't a good idea, especially when running this inside a CI pipeline. Further there is no way to access the password other than copying it from the logs.
I decided to add a new secret, to generate and store the admin password. This would open a breaking change, because the new secret must be generated.