colindean · colindean · Apr 29, 2022 · May 2, 2022 · May 2, 2022 · May 2, 2022
diff --git a/.chglog/CHANGELOG.tpl.md b/.chglog/CHANGELOG.tpl.md
diff --git a/.chglog/config.yml b/.chglog/config.yml
diff --git a/.env.example b/.env.example
@@ -9,23 +9,32 @@
 #                #
 ##################
 
-# These are used by the ui service
-# defined in the docker compose stack
+# These are used by the ui service defined in the docker compose stack
 
-# customize the location where you want users to provide feedback
+# customize the location for the Vela server address
 #
-# default: https://github.com/go-vela/ui/issues/new
-# VELA_FEEDBACK_URL=
+# Should match the "VELA_ADDR" value in docker-compose.yml when running locally.
+VELA_API=http://localhost:8080
 
 # customize the location where users can review documentation
 #
 # default: https://go-vela.github.io/docs
 # VELA_DOCS_URL=
 
-# customize the location for the Vela server address
+# customize the location where you want users to provide feedback
 #
-# Should match the "VELA_ADDR" value in docker-compose.yml when running locally.
-VELA_API=http://localhost:8080
+# default: https://github.com/go-vela/ui/issues/new
+# VELA_FEEDBACK_URL=
+
+# customize the number of bytes for size of logs the UI will attempt to render
+#
+# default: 20000 (2 MB)
+# VELA_LOG_BYTES_LIMIT=
+
+# customize the number of concurrent builds for a repo the UI will allow configuring
+#
+# default: 30
+# VELA_MAX_BUILD_LIMIT=
 
 ############################################################
 #  _______  _______  ______    __   __  _______  ______    #
@@ -38,16 +47,27 @@ VELA_API=http://localhost:8080
 #                                                          #
 ############################################################
 
-# These are used by the server service
-# defined in the docker compose stack
+# These are used by the server service defined in the docker compose stack
 
 # github web url (only required if using GitHub Enterprise)
 #
 # default: https://github.com
 # VELA_SCM_ADDR=
 
 # github client id from oauth application
-VELA_SCM_CLIENT=
+# VELA_SCM_CLIENT=
 
 # github client secret from oauth application
-VELA_SCM_SECRET=
+# VELA_SCM_SECRET=
+
+# COMPILER FLAGS
+#
+# compiler github is whether or not the compiler uses github to pull templates
+#
+# default: false
+# VELA_COMPILER_GITHUB=
+
+# compiler github url is the url used by the compiler to fetch templates
+#
+# default: https://github.com
+# VELA_COMPILER_GITHUB_URL
diff --git a/.github/CODE_OF_CONDUCT.md b/.github/CODE_OF_CONDUCT.md
diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md
@@ -1,29 +1,14 @@
 # Contributing
 
-We'd love to accept your contributions to this project!
-
-There are just a few guidelines you need to follow.
-
-## Bugs
-
-Bug reports should be opened up as [issues](https://help.github.com/en/github/managing-your-work-on-github/about-issues) on the [go-vela/community](https://github.com/go-vela/community) repository!
-
-## Feature Requests
-
-Feature Requests should be opened up as [issues](https://help.github.com/en/github/managing-your-work-on-github/about-issues) on the [go-vela/community](https://github.com/go-vela/community) repository!
-
-## Pull Requests
-
-**NOTE: We recommend you start by opening a new issue describing the bug or feature you're intending to fix. Even if you think it's relatively minor, it's helpful to know what people are working on.**
-
-We are always open to new PRs! You can follow the below guide for learning how you can contribute to the project!
-
 ## Getting Started
 
+We'd love to accept your contributions to this project! If you are a first time contributor, please review our [Contributing Guidelines](https://go-vela.github.io/docs/community/contributing_guidelines/) before proceeding.
+
 ### Prerequisites
 
-* [Review the commit guide we follow](https://chris.beams.io/posts/git-commit/#seven-rules) - ensure your commits follow our standards
 * [Review the local development docs](../DOCS.md) - ensures you have the Vela application stack running locally
+* [Review the commit guide we follow](https://chris.beams.io/posts/git-commit/#seven-rules) - ensure your commits follow our standards
+* [Review our style guide](https://go-vela.github.io/docs/community/contributing_guidelines/#style-guide) to ensure your code is clean and consistent.
 
 ### Setup
 
@@ -62,23 +47,6 @@ cd $HOME/go-vela/server
 ```
 
 * Write your code and tests to implement the changes you desire.
-  * Please be sure to [follow our commit rules](https://chris.beams.io/posts/git-commit/#seven-rules)
-  * Please address linter warnings appropriately. If you are intentionally violating a rule that triggers a linter, please annotate the respective code with `nolint` declarations [[docs](https://golangci-lint.run/usage/false-positives/)]. we are using the following format for `nolint` declarations:
-
-    ```go
-    // nolint:<linter(s)> // <short reason>
-    ```
-
-    Example:
-
-    ```go
-    // nolint:gocyclo // legacy function is complex, needs simplification
-    func superComplexFunction() error {
-      // ..
-    }
-    ```
-
-    Check the [documentation for more examples](https://golangci-lint.run/usage/false-positives/).
 
 * Run the repository code (ensures your changes perform as you desire):
 
@@ -105,28 +73,9 @@ make clean
 
 ```bash
 # push your code up to your fork
-git push fork master
+git push fork main
 ```
 
-* Open a pull request!
-  * For the title of the pull request, please use the following format for the title:
-
-    ```text
-    feat(wobble): add hat wobble
-    ^--^^------^  ^------------^
-    |   |         |
-    |   |         +---> Summary in present tense.
-    |   +---> Scope: a noun describing a section of the codebase (optional)
-    +---> Type: chore, docs, feat, fix, refactor, or test.
-    ```
-
-    * feat: adds a new feature (equivalent to a MINOR in Semantic Versioning)
-    * fix: fixes a bug (equivalent to a PATCH in Semantic Versioning)
-    * docs: changes to the documentation
-    * refactor: refactors production code, eg. renaming a variable; doesn't change public API
-    * test: adds missing tests, refactors tests; no production code change
-    * chore: updates something without impacting the user (ex: bump a dependency in package.json or go.mod); no production code change
-
-    If a code change introduces a breaking change, place ! suffix after type, ie. feat(change)!: adds breaking change. correlates with MAJOR in semantic versioning.
+* Make sure to follow our [PR process](https://go-vela.github.io/docs/community/contributing_guidelines/#development-workflow) when opening a pull request
 
 Thank you for your contribution!
diff --git a/.github/README.md b/.github/README.md
@@ -3,7 +3,7 @@
 [![license](https://img.shields.io/crates/l/gl.svg)](../LICENSE)
 [![GoDoc](https://godoc.org/github.com/go-vela/server?status.svg)](https://godoc.org/github.com/go-vela/server)
 [![Go Report Card](https://goreportcard.com/badge/go-vela/server)](https://goreportcard.com/report/go-vela/server)
-[![codecov](https://codecov.io/gh/go-vela/server/branch/master/graph/badge.svg)](https://codecov.io/gh/go-vela/server)
+[![codecov](https://codecov.io/gh/go-vela/server/branch/main/graph/badge.svg)](https://codecov.io/gh/go-vela/server)
 
 > Vela is in active development and is a pre-release product.
 >

diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml
@@ -10,11 +10,18 @@ on:
 jobs:
   build:
     runs-on: ubuntu-latest
-    container:
-      image: golang:1.17
+
     steps:
     - name: clone
-      uses: actions/checkout@v2
+      uses: actions/checkout@v3
+
+    - name: install go
+      uses: actions/setup-go@v4
+      with:
+        # use version from go.mod file
+        go-version-file: 'go.mod'
+        cache: true
+        check-latest: true
 
     - name: build
       run: |

diff --git a/.github/workflows/codeql-analysis.yml b/.github/workflows/codeql-analysis.yml
@@ -13,10 +13,10 @@ name: "CodeQL"
 
 on:
   push:
-    branches: [ master ]
+    branches: [ main ]
   pull_request:
     # The branches below must be a subset of the branches above
-    branches: [ master ]
+    branches: [ main ]
   schedule:
     - cron: '23 1 * * 0'
 
@@ -35,11 +35,11 @@ jobs:
 
     steps:
     - name: Checkout repository
-      uses: actions/checkout@v2
+      uses: actions/checkout@v3
 
     # Initializes the CodeQL tools for scanning.
     - name: Initialize CodeQL
-      uses: github/codeql-action/init@v1
+      uses: github/codeql-action/init@v2
       with:
         languages: ${{ matrix.language }}
         # If you wish to specify custom queries, you can do so here or in a config file.
@@ -50,7 +50,7 @@ jobs:
     # Autobuild attempts to build any compiled languages  (C/C++, C#, or Java).
     # If this step fails, then you should remove it and run the build manually (see below)
     - name: Autobuild
-      uses: github/codeql-action/autobuild@v1
+      uses: github/codeql-action/autobuild@v2
 
     # ℹ️ Command-line programs to run using the OS shell.
     # 📚 https://git.io/JvXDl
@@ -64,4 +64,4 @@ jobs:
     #   make release
 
     - name: Perform CodeQL Analysis
-      uses: github/codeql-action/analyze@v1
+      uses: github/codeql-action/analyze@v2