Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* add a test workflow * also run on release * add git config * add the docker-updatinator image * use v2 checkout(?) * add write permissions to the bot * run as root if this doesn't work, i will remove the updatinator container and re-test with the write permissions granted * add an ssh key to authenticate for whoami test * login to github with the right token * remove quay container and just use gh * set auth token perms to read all although we're overriding the token later, so this might not do anything * remove permissions entirely we shouldn't need it if we're overwriting the GITHUB_TOKEN * re-add write permissions * move the git config higher and output the status to see if we can figure out why we're getting bad credentials again * export the gh token * unset the existing GITHUB_TOKEN before using ours * make it a separate step also remove the permissions which might be why we're getting the message, too * also unset and export GH_TOKEN * use the actual token rather than variable we exported * allow ssh for debugging * move tmate to after failing test * allow other users to ssh in * maybe switching to false will actually let us log in? * try not running whoami we'll probably fail the tests but we can see if it's needed * I guess put stuff in here since we committed it to vc * add unset to the regular script * remove typo * remove --with-token * set tokens as env variables in the job * remove tmate couldn't get it to work * add tokens to test steps, too * unset tokens again * maybe don't need to auth? * okay, let's whoami with this token * use php 7.4 * install php 7.4 earlier * add mariadb for wp tests * add custom db name * define empty password for root user * use the updatinator container * grant write permissiosn * use container as root * pass env variables into the test step * install wp-cli * remove the root password since it's not part of the fixture * test the database * set root password to empty * try connecting with root password * set password to empty string * more database setup * change how we set the password * don't use PASSWORD() * remove the password for the blank password test * don't create the database * remove test workflow since it's converted to gha * rename deploy to publish * set test to run on tag creation rather than release creation * send dispatch so releases are chained from tests * change the trigger to repository_dispatch this should trigger only on tag creation after the tests have run * change the job name to publish * setup php this is mostly for composer purposes * get the tag name that was just created * publish the release * build the update-tool.phar * upload the phar to the release * delete circle workflow * Use GitHub test badge * update notes * use checkout@v3 * use a non-deprecated release action * one does not simply create a new tag Co-authored-by: Phil Tyler <[email protected]> --------- Co-authored-by: Phil Tyler <[email protected]>
- Loading branch information
1 parent
d26aaf4
commit 5cbbbfa