gh-at

View documentation for the original command

$ tldr gh attestation

As gh-at is not a standard command, a precise synopsis does not exist. Conceptually, if such a command were implemented as a wrapper, its usage would likely involve:
gh-at [at_options] -- [gh_options] [gh_arguments]
This structure implies providing a time for execution, optional `at` command flags (e.g., for mailing output), a separator (`--`), and then the complete `gh` command (e.g., `gh pr merge --auto`).

    Required. Defines when the `gh` command should be executed. Examples: `now + 1 hour`, `tomorrow`, `10:00 AM July 24`.

-q queue
    Optional. Specifies the queue to use for the job. Lowercase letters are processed by `at`, uppercase by `batch` (usually default `a`).

-m
    Optional. Send mail to the user after the `gh` command has been executed, even if there is no output.

--
    Required. A standard convention used to separate options from arguments, indicating that subsequent arguments are not options for `gh-at` itself, but rather the command and arguments to be passed to the underlying `gh` utility.


    Required. The specific GitHub CLI command to be executed, e.g., `pr merge`, `issue close`.


    Optional. Any options specific to the `gh` command being run, e.g., `--auto` for `gh pr merge`.


    Optional. Any arguments specific to the `gh` command being run, e.g., a pull request number.

The gh-at command is not a standard, recognized standalone Linux command. It appears to be a hypothetical combination of two distinct utilities often used together conceptually:

1. gh: The official GitHub command-line interface, which allows users to interact with GitHub repositories, pull requests, issues, and more directly from the terminal.
2. at: A standard Unix/Linux command used to schedule commands to be executed once at a particular time in the future.

If gh-at were to exist, it would conceptually enable the scheduling of GitHub CLI operations. For instance, one might want to schedule a `gh pr merge` command to run at a specific time, or automatically fetch repository updates with `gh repo sync`. Such functionality is typically achieved by writing a shell script that incorporates gh commands and then scheduling that script using the at command.

The most significant caveat is that gh-at is not a real, standard Linux command. Attempting to execute `gh-at` directly will result in a 'command not found' error unless a custom script with this name has been created and placed in the system's PATH. Users should instead construct their desired GitHub CLI operations and schedule them explicitly using the at command or cron for recurring tasks.

Users can achieve the conceptual functionality of 'gh-at' by combining at with gh inside a shell script or directly via the `at` command.

Example: Merging a PR in 30 minutes
echo 'gh pr merge 123 --auto --delete-branch' | at now + 30 minutes

Example: Closing an issue tomorrow at 9 AM with a script
#!/bin/bash
gh issue close 456 --reason 'not planned' -c 'Closing due to project reprioritization.'

Save this as `close_issue.sh` and make it executable (`chmod +x close_issue.sh`). Then schedule:
echo '~/close_issue.sh' | at 09:00 tomorrow

Ensure that the environment where the `at` job runs (especially PATH and authentication tokens for `gh`) is correctly set up for the commands to execute successfully.

There is no specific history for a command named gh-at as it does not exist as a standalone utility. However, the components have their own histories:

gh: The GitHub CLI was officially released in September 2020, providing a modern interface for GitHub from the terminal, building upon previous community efforts and internal GitHub tools.

at: The `at` command has been a staple of Unix-like operating systems for decades, providing a simple mechanism for one-time job scheduling. Its origins can be traced back to early Unix versions.

gh(1), at(1), cron(8), batch(1)