2022-03-11 16:43:49 +00:00
parent c6a578b5bb
commit c00037d3f6
12 changed files with 18 additions and 0 deletions
							
							
							
						
@@ -1,43 +0,0 @@
# Introduction
### Welcome!
First off, thank you for considering contributing to FHeD!
### Project philosophy
We wanted to create a simple, easy to use, free helpdesk system without all of the extra bells and whistles that some individuals and small companies may not require.
### Roadmap
If you want to know more about the project direction or looking for something to work on, checkout the [roadmap](https://github.com/luketainton/FHeD#Roadmap)!
Feel free to open an issue if you have any questions.
# Ground Rules
### Code of conduct and guidelines
First of all, we expect everyone (contributors and maintainers alike) to respect the [Code of conduct](https://github.com/luketainton/FHeD/blob/master/.github/CODE_OF_CONDUCT.md). It is not a recommendation, it is mandatory.
For all contributions, please respect the following guidelines:
* Each pull request should implement ONE feature or bugfix. If you want to add or fix more than one thing, submit more than one pull request.
* Do not commit changes to files that are irrelevant to your feature or bugfix (eg: `.gitignore`).
* Do not add unnecessary dependencies.
* Be aware that the pull request review process is not immediate, and is generally proportional to the size of the pull request.
# Getting started
### Discuss about ideas
If you want to add a feature, it's often best to talk about it before starting working on it and submitting a pull request. It's not mandatory at all, but
feel free to open an issue to present your idea.
### How to submit a contribution
The general process to submit a contribution is as follow:
1. Create your own fork of the code
2. Make you changes in a new branch in your fork (not main)
3. Make sure to fill the [pull request](https://github.com/luketainton/FHeD/blob/master/.github/PULL_REQUEST_TEMPLATE/pull_request_template.md) properly.
### Happy coding :metal:
							
							
							
						
@@ -1,38 +0,0 @@
---
name: Bug report
about: Create a report to help us improve
title: '🐛'
labels: type:bug
assignees:
---
**Describe the bug**
A clear and concise description of what the bug is.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Desktop (please complete the following information):**
 - OS: [e.g. iOS]
 - Browser: [e.g. chrome, safari]
 - Version: [e.g. 22]
**Smartphone (please complete the following information):**
 - Device: [e.g. iPhone6]
 - OS: [e.g. iOS8.1]
 - Browser: [e.g. stock browser, safari]
 - Version: [e.g. 22]
**Additional context**
Add any other context about the problem here.
							
							
							
						
@@ -1,20 +0,0 @@
---
name: Document request
about: Request a change to documentation
title: '📚'
labels: type:docs
assignees:
---
**Is your request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.
							
							
							
						
@@ -1,20 +0,0 @@
---
name: Feature request
about: Suggest an idea for this project
title: '✨'
labels: type:feature
assignees:
---
**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.
							
							
							
						
@@ -1,15 +0,0 @@
mode: auto
silent: false
branchName: '${issue.number}'
branches:
  - label: type:feature
    prefix: feat-
  - label: type:bug
    prefix: bug-
  - label: type:epic
    prefix: epic-
  - label: type:docs
    prefix: docs-
  - label: type:automation
    prefix: auto-
autoCloseIssue: true
							
							
							
						
@@ -1,17 +0,0 @@
## Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes # (issue)
## Type of change
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
## Checklist:
- [ ] I read & comply with the [contributing guidelines](https://github.com/luketainton/FHeD/blob/main/.github/CONTRIBUTING.md)
- [ ] I have tested my code for new features & regressions on both mobile & desktop devices, using the latest version of major browsers.
- [ ] I have made corresponding changes the documentation (README.md).
							
							
							
						
@@ -1,14 +0,0 @@
name: Auto-create branches
on:
    issues:
        types: [assigned]
jobs:
    create_issue_branch_job:
        runs-on: ubuntu-latest
        steps:
        - name: Create Issue Branch
          uses: robvanderleek/create-issue-branch@master
          env:
            GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
							
							
							
						
@@ -1,39 +0,0 @@
name: Deploy
on:
  push:
    branches: main
jobs:
  release-on-push:
    runs-on: ubuntu-latest
    outputs: 
      ver: ${{ steps.release.outputs.version }}
      tag: ${{ steps.release.outputs.tag_name }}
    env:
      GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
    steps:
      - name: Get Release
        id: release
        uses: rymndhng/release-on-push-action@master
        with:
          bump_version_scheme: patch
      - name: Check Release Output
        id: rop-check
        run: |
          echo "Got tag name ${{ steps.release.outputs.tag_name }}"
          echo "Got release version ${{ steps.release.outputs.version }}"
  build:
    name: GitHub Container Registry
    runs-on: ubuntu-latest
    needs: [prepare-data]
    steps:
    - uses: actions/checkout@v2
    - name: Login to GitHub Container Registry
      run: echo ${{ secrets.PAT }} | docker login ghcr.io -u luketainton --password-stdin
    - name: Build image for GitHub Container Registry
      run: docker build . --file Dockerfile --tag ghcr.io/luketainton/fhed:${{ needs.release-on-push.outputs.ver }} --tag ghcr.io/luketainton/fhed:latest
    - name: Push image to GitHub Container Registry
      run: |
        docker push ghcr.io/luketainton/fhed:latest
        docker push ghcr.io/luketainton/fhed:${{ needs.release-on-push.outputs.ver }}
							
							
							
						
@@ -1,13 +0,0 @@
name: Greetings
on: [pull_request, issues]
jobs:
  greeting:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/first-interaction@v1
      with:
        repo-token: ${{ secrets.GITHUB_TOKEN }}
        issue-message: 'Welcome! Thank you for opening your first issue on FHeD. Please see the [contributing guidelines](https://github.com/luketainton/FHeD/blob/main/.github/CONTRIBUTING.md) for more information.'
        pr-message: 'Thank you for opening your first pull request on FHeD! Please see the [contributing guidelines](https://github.com/luketainton/FHeD/blob/main/.github/CONTRIBUTING.md) to ensure your PR is ready for merge.'
							
							
							
						
@@ -1,19 +0,0 @@
name: Stale issues and PRs
on:
  schedule:
  - cron: "0 0 * * *"
jobs:
  stale:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/stale@v4
      with:
        repo-token: ${{ secrets.GITHUB_TOKEN }}
        stale-issue-message: 'This issue has been marked as stale due to inactivity. If this issue is still ongoing, please leave a comment.'
        stale-pr-message: 'This pull request has been marked as stale due to inactivity. If this issue is still ongoing, please leave a comment.'
        stale-issue-label: 'status:stale'
        stale-pr-label: 'status:stale'