Update code of conduct

CODE_OF_CONDUCT.md

@@ -1,2 +1,2 @@
-This project is governed by [Lyft's code of conduct](https://github.com/lyft/code-of-conduct).
+This project is governed by LF AI Foundation's [code of conduct](https://lfprojects.org/policies/code-of-conduct/). 
 All contributors and participants agree to abide by its terms.

boilerplate/flyte/code_of_conduct/CODE_OF_CONDUCT.md

@@ -0,0 +1,2 @@
+This project is governed by LF AI Foundation's [code of conduct](https://lfprojects.org/policies/code-of-conduct/). 
+All contributors and participants agree to abide by its terms.

boilerplate/flyte/code_of_conduct/README.rst

@@ -0,0 +1,2 @@
+CODE OF CONDUCT
+~~~~~~~~~~~~~~~

boilerplate/flyte/code_of_conduct/update.sh

@@ -0,0 +1,12 @@
+#!/usr/bin/env bash
+
+# WARNING: THIS FILE IS MANAGED IN THE 'BOILERPLATE' REPO AND COPIED TO OTHER REPOSITORIES.
+# ONLY EDIT THIS FILE FROM WITHIN THE 'FLYTEORG/BOILERPLATE' REPOSITORY:
+# 
+# TO OPT OUT OF UPDATES, SEE https://github.com/flyteorg/boilerplate/blob/master/Readme.rst
+
+set -e
+
+DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" >/dev/null && pwd )"
+
+cp ${DIR}/CODE_OF_CONDUCT.md ${DIR}/../../../CODE_OF_CONDUCT.md

boilerplate/flyte/golang_test_targets/goimports

@@ -5,4 +5,4 @@
 # 
 # TO OPT OUT OF UPDATES, SEE https://github.com/flyteorg/boilerplate/blob/master/Readme.rst
 
-goimports -w $(find . -type f -name '*.go' -not -path "./vendor/*" -not -path "./pkg/client/*")
+goimports -w $(find . -type f -name '*.go' -not -path "./vendor/*" -not -path "./pkg/client/*" -not -path "./boilerplate/*")

boilerplate/flyte/pull_request_template/pull_request_template.md

@@ -1,8 +1,9 @@
-## Read then delete
+## _Read then delete this section_
 
-- Make sure to use a concise title for the pull-request.
-- Use #patch, #minor or #major in the pull-request title to bump the corresponding version. Otherwise, the patch version
-will be bumped. [More details](https://github.com/marketplace/actions/github-tag-bump)
+_- Make sure to use a concise title for the pull-request._
+
+_- Use #patch, #minor or #major in the pull-request title to bump the corresponding version. Otherwise, the patch version
+will be bumped. [More details](https://github.com/marketplace/actions/github-tag-bump)_
 
 # TL;DR
 _Please replace this text with a description of what this PR accomplishes._
@@ -24,7 +25,9 @@ _Please replace this text with a description of what this PR accomplishes._
  _How did you fix the bug, make the feature etc. Link to any design docs etc_
 
 ## Tracking Issue
-https://github.com/flyteorg/flyte/issues/<number>
+_Remove the '*fixes*' keyword if there will be multiple PRs to fix the linked issue_
+
+fixes https://github.com/flyteorg/flyte/issues/<number>
 
 ## Follow-up issue
 _NA_

boilerplate/update.cfg

@@ -4,4 +4,4 @@ flyte/golang_support_tools
 flyte/pull_request_template
 flyte/welcome_bot
 flyte/precommit
-
+flyte/code_of_conduct

pull_request_template.md

@@ -1,8 +1,9 @@
-## Read then delete
+## _Read then delete this section_
 
-- Make sure to use a concise title for the pull-request.
-- Use #patch, #minor or #major in the pull-request title to bump the corresponding version. Otherwise, the patch version
-will be bumped. [More details](https://github.com/marketplace/actions/github-tag-bump)
+_- Make sure to use a concise title for the pull-request._
+
+_- Use #patch, #minor or #major in the pull-request title to bump the corresponding version. Otherwise, the patch version
+will be bumped. [More details](https://github.com/marketplace/actions/github-tag-bump)_
 
 # TL;DR
 _Please replace this text with a description of what this PR accomplishes._
@@ -24,7 +25,9 @@ _Please replace this text with a description of what this PR accomplishes._
  _How did you fix the bug, make the feature etc. Link to any design docs etc_
 
 ## Tracking Issue
-https://github.com/flyteorg/flyte/issues/<number>
+_Remove the '*fixes*' keyword if there will be multiple PRs to fix the linked issue_
+
+fixes https://github.com/flyteorg/flyte/issues/<number>
 
 ## Follow-up issue
 _NA_