feat: Add support for schedule trigger (#12)

Enables using `schedule` event

Author: iRoachie

README.md

@@ -11,6 +11,7 @@ We currently support:
 - `pull_request`
 - `release`
 - `push` (tags, commits)
+- `schedule`
 
 ## Messages
 
@@ -58,6 +59,10 @@ All event messages will have these elements:
 1. Commit Hash - Also a link showing combined changes of all commits for the push
 2. Head Commit name - Name of last commit in the batch (can push multiple commits). Also a link to that commit.
 
+### Schedule
+
+![Schedule](https://user-images.githubusercontent.com/5962998/100387966-baad0800-2fff-11eb-8733-56c4400286fa.png)
+
 ## Usage
 
 You can use this action after any other action, however I recommend you put it as the last one. Here is an example setup of this action for a pull request:

dist/index.js

@@ -12839,6 +12839,11 @@ const getMessage = () => {
         return `Workflow <${runUrl}|${process.env.GITHUB_WORKFLOW}> (<${github.context.payload.compare}|${commitId}>) for Commit <${headCommit.url}| ${headCommit.title}>`;
       }
 
+    case 'schedule':
+      {
+        return `Scheduled Workflow <${runUrl}|${process.env.GITHUB_WORKFLOW}>`;
+      }
+
     default:
       return null;
   }

src/notify.ts

@@ -83,6 +83,10 @@ const getMessage = () => {
       return `Workflow <${runUrl}|${process.env.GITHUB_WORKFLOW}> (<${context.payload.compare}|${commitId}>) for Commit <${headCommit.url}| ${headCommit.title}>`;
     }
 
+    case 'schedule': {
+      return `Scheduled Workflow <${runUrl}|${process.env.GITHUB_WORKFLOW}>`;
+    }
+
     default:
       return null;
   }