Currently the project relies on a hardcoded ALLOWED_USERNAME environment variable to see if it should respond. But the GitHub webhook payload includes information about the user's association with the repo. We should use that instead of the hardcoded username.
Currently the project relies on a hardcoded ALLOWED_USERNAME environment variable to see if it should respond. But the GitHub webhook payload includes information about the user's association with the repo. We should use that instead of the hardcoded username.
@Aiderbot can you have a look at this?