From 98b01acf0ec71b6bb3fcabe2958d99cb8bf17609 Mon Sep 17 00:00:00 2001 From: Jonny Read Date: Tue, 4 Jul 2023 15:49:55 +0100 Subject: [PATCH 1/2] Fix syntax, link and grammar in `deployment.rst` (#722) --- docs/deployment.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/deployment.rst b/docs/deployment.rst index f2cad4ae..1fb9e7cb 100644 --- a/docs/deployment.rst +++ b/docs/deployment.rst @@ -47,7 +47,7 @@ Running Locally 6. Add a repository for your Github app by going to `application settings `_ 7. Do a test pull request to check if everything is working -Note: if you wish to use a different config file name beside `mergeable.yml`, use `CONFIG_PATH` environment variable. Config files uses `.github` as base path, see [here](https://github.com/probot/probot/blob/1a19bdd/src/context.ts#L190) +Note: if you wish to use a different config file name besides ``mergeable.yml``, use the ``CONFIG_PATH`` environment variable. Config files use ``.github`` as base path, see `here `_. Possible Issues From 07698d30a3b300ae3cc6d37591d26605cf15ede6 Mon Sep 17 00:00:00 2001 From: Jonny Read Date: Tue, 4 Jul 2023 15:50:10 +0100 Subject: [PATCH 2/2] Update CONTRIBUTING.md link syntax for style guide (#723) --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 3463c2ef..e04f991d 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -21,7 +21,7 @@ Please note that this project is released with a [Contributor Code of Conduct][c Here are a few things you can do that will increase the likelihood of your pull request being accepted: -- Follow the [style guide][https://standardjs.com/] which is using standard. Any linting errors will be shown when running `npm test` +- Follow the [style guide](https://standardjs.com/) which is using standard. Any linting errors will be shown when running `npm test` - Write and update tests. - Keep your change as focused as possible. If there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as separate pull requests. - Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).