Fix markdown typos

[janosh]

Follow up to #1283.

[janosh]

run jenkins

[Andrew-S-Rosen]

@janosh: It works!!! Thank you! I just have to work on getting the build logs public, but this solves it. And thanks for your markdown fixes :)

Note to self: We have to rely on a whitelist to ensure people don't run arbitrary, unseen code on the cluster. I manually added @janosh to the whitelist and anyone in @Quantum-Accelerators. However, for everyone else, we have the bot post a message that has to be approved by a maintainer ("ok to test"), after which the trigger phrase can be used.

[janosh]

@Andrew-S-Rosen You could also use something like what GitHub uses to determine whether CI is allowed to run on a PR. It checks if "author_association" == "FIRST_TIME_CONTRIBUTOR" and if so waits for a maintainer to explicitly give CI approval.

Might save you the hassle of maintaining a white list.

import requests

def is_first_time_contributor(owner, repo, pr_number, access_token):
    headers = {
        "Authorization": f"token {access_token}",
        "Accept": "application/vnd.github.v3+json"
    }
    url = f"https://api.github.com/repos/{owner}/{repo}/pulls/{pr_number}"

    response = requests.get(url, headers=headers)
    if response.status_code == 200:
        pr_info = response.json()
        return pr_info.get("author_association") == "FIRST_TIME_CONTRIBUTOR"
    else:
        raise Exception(f"GitHub API error: {response.status_code}")

[Andrew-S-Rosen]

@janosh: Thanks! That's good to know.

The are reasons related to security that it's important to strictly maintain a whitelist. Even if a PR looks safe, someone can then follow it up with a malicious commit once given approval. Still sorting out the logistics of how I want to handle this, but your PRs helped me figure out a few of the logistics on the backend.

Either way, the regular test suite always runs on PRs like normal.