ansible/ansibullbot

Name: ansibullbot

Owner: Ansible

Description: Bot for management of Ansible issues and PRs in Github

Created: 2015-11-10 18:11:34.0

Updated: 2018-01-12 15:04:21.0

Pushed: 2018-01-09 00:41:46.0

Homepage:

Size: 23673

Language: Python

GitHub Committers

User	Most Recent Commit	# Commits

Other Committers

User	Email	Most Recent Commit	# Commits

README

Ansibull Github Issue/Pullrequest Bot

https://galaxy.ansible.com/samdoran/ansibullbot/

triage.py --help
e: triage.py [-h] [--skip_no_update] [--skip_no_update_timeout]
             [--collect_only] [--skip_module_repos] [--module_repos_only]
             [--force_rate_limit] [--sort {asc,desc}] [--logfile LOGFILE]
             [--daemonize] [--daemonize_interval DAEMONIZE_INTERVAL]
             [--skiprepo SKIPREPO] [--repo REPO] [--only_prs]
             [--only_issues] [--only_open] [--only_closed] [--verbose]
             [--dry-run] [--force] [--safe_force] [--debug] [--pause]
             [--ignore_state] [--issue_component_matching] [--pr PR]
             [--start-at START_AT] [--no_since]

ge issue and pullrequest queues for Ansible. (NOTE: only useful if you
 commit access to the repo in question.)

onal arguments:
, --help            show this help message and exit
skip_no_update      skip processing if updated_at hasn't changed
skip_no_update_timeout
                    ignore skip if last process is X days old
collect_only        stop after caching issues
skip_module_repos   ignore the module repos
module_repos_only   only process the module repos
force_rate_limit    debug: force the rate limit
sort {asc,desc}     Direction to sort issues [desc=9-0 asc=0-9]
logfile LOGFILE     Send logging to this file
daemonize           run in a continuos loop
daemonize_interval DAEMONIZE_INTERVAL
                    seconds to sleep between loop iterations
skiprepo SKIPREPO   Github repo to skip triaging
repo REPO, -r REPO  Github repo to triage (defaults to all)
only_prs            Triage pullrequests only
only_issues         Triage issues only
only_open           Triage open issues|prs only
only_closed         Triage closed issues|prs only
verbose, -v         Verbose output
dry-run, -n         Don't make any changes
force, -f           Do not ask questions
safe_force          Prompt only on specific actions
debug, -d           Debug output
pause, -p           Always pause between prs|issues
ignore_state        Do not skip processing closed issues
issue_component_matching
                    Try to enumerate the component labels for issues
pr PR, --id PR      Triage only the specified pr|issue (separated by
                    commas)
start-at START_AT, --resume_id START_AT
                    Start triage at the specified pr|issue
no_since            Do not use the since keyword to fetch issues

If you are looking for help, please see the ISSUE HELP