eddiehubcommunity / template Goto Github PK

The workflow community.yml is referencing action actions/checkout using references v1. However this reference is missing the commit a6747255bd19d7a757dbdda8c654a9f84db19839 which may contain fix to the some vulnerability.
The vulnerability fix that is missing by actions version could be related to:
(1) CVE fix
(2) upgrade of vulnerable dependency
(3) fix to secret leak and others.
Please consider to update the reference to the action.

Change to http://discord.eddiehub.org

• .github/workflows/ISSUE_TEMPLATES/feature.md

If people are ready to contribute, we'll need a doc with guidelines on how to do so. Additionally, I'd suggest adding/linking a guide on how GitHub Actions work, and how to modify the same, so that those who are new have a place to get started

This idea comes from an Issue in the EddieBot repo, Issue #316.

We should add templates for Issues such as a template for idea, feature, fix, etc.

Additionaly, in the EddieBot repo there is a template for a bug type of issue.
@eddiejaoude mentioned in Issue #316 that we should add templates in this repo template for better scalability. We might want to move that here or make a bug issue template here as well.

I would like to handle this, but first I have to learn about GitHub Actions as I just got into Github and don't know too much about it.

Please share any thoughts on the matter.:yum:

This repo should have a Pull Request Template

I will update the issue-message, Pr-Message, with new ones and add a footer message in Community.yml

The workflow stale.yml is referencing action actions/stale using references v1. However this reference is missing the commit af4072615903a8b031f986d25b1ae3bf45ec44d4 which may contain fix to the some vulnerability.
The vulnerability fix that is missing by actions version could be related to:
(1) CVE fix
(2) upgrade of vulnerable dependency
(3) fix to secret leak and others.
Please consider to update the reference to the action.

For example, if we update the CONTRIBUTING.md file in here, we should have an Action which runs on other repos on every change to check if this file has been updated here and then it updates it in the other repo the Action is running in.

In github actions there is the possibility to run a action if the run fails

Github action <- creates issue with labels and assignee

- uses: nashmaniac/[email protected]
  if: ${{ failure() }} # only run when this job is failed.
  name: Create Issue Action
  with:
    title: Linter Failed
    token: ${{secrets.GITHUB_TOKEN}}
    assignees: ${{github.actor}}
    labels: refactoring-needed, help needed
    body: Workflow failed for commit ${{github.sha}}