![]() # Use a repository search to find repositories to target (GitHub only). ![]() # Include repositories that match with a given Regular Expression repo-include: other-org/python-repo # Exclude repositories that match with a given Regular Expression repo-exclude: group/project # The name, including owner of a GitHub repository in the format "ownerName/repoName". # The name, including owner of a GitLab project in the format "ownerName/repoName". Will default to the first line of the commit message if none is set. Will default to everything but the first line of the commit message if none is set. platform: github # The body of the commit message. Available values: github, gitlab, gitea, bitbucket_server. plain-output: false # The platform that is used. output: "- " # Don't use any terminal formatting when printing the output. example # The file that the output of the script should be outputted to. All repositories in that organization will be used. max-reviewers: 0 # If this value is set, team reviewers will be randomized max-team-reviewers: 0 # The name of a GitHub organization. log-level: info # If this value is set, reviewers will be randomized. Available values: trace, debug, info, error. log-format: text # The level of logging that should be made. Available values: text, json, json-pretty. log-file: "- " # The formatting of the logs. example # The file where all logs should be printed to. interactive: false # Labels to be added to any created pull request. insecure: false # Take manual decision before committing any change. include-subgroups: false # Insecure controls whether a client verifies the server certificate chain and host name. example # Include GitLab subgroups when using the -group flag. All repositories in that group will be used. git-type: go # The name of a GitLab organization. This requires git to be installed and available with by calling "git". This is compiled with the multi-gitter binary, and no extra dependencies are needed. # Available values: # go: Uses go-git, a Go native implementation of git. Default behavior is for the fork to be on the logged in user. fork: false # If set, make the fork to the defined value. fetch-depth: 1 # Fork the repository instead of creating a new branch on the same owner. dry-run: false # Limit fetching to the specified number of commits. ![]() draft: false # Run without pushing changes or creating pull requests. conflict-strategy: skip # Create pull request(s) as draft. # replace: Replace the existing content of the branch by force pushing any new changes, then reuse any existing pull request, or create a new one if none exist. # Available values: # skip: Skip making any changes to the existing branch and do not create a new pull request. concurrent: 1 # What should happen if the branch already exist. Will default to title + body if none is set. See the GitHub documentation for full syntax. Repeated results from a given repository will be ignored, forks are NOT included by default (use `fork:true` to include them). branch: multi-gitter-branch # Use a code search to find a set of repositories to target (GitHub only). # The name of the branch where changes are committed. # Base URL of the target platform, needs to be changed for GitHub enterprise, a self-hosted GitLab instance, Gitea or BitBucket. # The branch which the changes will be based on. If not set, the global git config setting will be used. # The username of the assignees to be added on the pull request. The priority of configs are first flags, then defined config file and lastly the static config file. Multi-gitter will also read from the file ~/.multi-gitter/config and take and configuration from there. If you want to use a configuration file, simply use the -config=./path/to/config.yaml. In Gitea, access tokens can be generated under Settings -> Applications -> Manage Access Tokens Config fileĪll configuration in multi-gitter can be done through command line flags, configuration files or a mix of both. Make sure to give to it the api permission. How to generate a GitLab personal access token. ![]() How to generate a GitHub personal access token. This token can either be set in the GITHUB_TOKEN, GITLAB_TOKEN, GITEA_TOKEN environment variable, or by using the -token flag. To use multi-gitter, a token that is allowed to list repositories and create pull requests is needed. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |