Made dedup_key usage consistent with integration key

README.md

@@ -15,7 +15,7 @@ Sends a critical PagerDuty alert, e.g. on action failure.
 
 **Required:** the integration key for your PagerDuty service
 
-`dedup_key`
+`pagerduty-dedup-key`
 
 **Optional:** a `dedup_key` for your alert. This will enable PagerDuty to coalesce multiple alerts into one.
 More documentation is available [here](https://developer.pagerduty.com/docs/events-api-v2/trigger-events/).
@@ -30,5 +30,5 @@ In your `steps`:
   uses: Entle/[email protected]
   with:
     pagerduty-integration-key: '${{ secrets.PAGERDUTY_INTEGRATION_KEY }}'
-    dedup_key: github_workflow_failed
+    pagerduty-dedup-key: github_workflow_failed
 ```

action.yml

@@ -4,8 +4,8 @@ inputs:
   pagerduty-integration-key:
     description: 'The integration key for your PagerDuty service'
     required: true
-  dedup_key:
-    description: 'The key used to correlate triggers, acknowledges, and resolves for the same alert.'
+  pagerduty-dedup-key:
+    description: 'The key used to correlate PagerDuty triggers, acknowledges, and resolves for the same alert.'
     required: false
 runs:
   using: 'node12'

index.js

@@ -39,9 +39,9 @@ try {
     routing_key: integrationKey,
     event_action: 'trigger',
   };
-  const dedup_key = core.getInput('dedup_key');
-  if (dedup_key != '') {
-    alert.dedup_key = dedup_key;
+  const dedupKey = core.getInput('pagerduty-dedup-key');
+  if (dedupKey != '') {
+    alert.dedup_key = dedupKey;
   }
   sendAlert(alert);
 } catch (error) {