CODEOWNERS :::

 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

You can use a CODEOWNERS file to define individuals or teams that are responsible for code in a repository.

People with admin or owner permissions can set up a CODEOWNERS file in a repository.

Code owners are automatically requested for review when someone opens a pull request that modifies code that they own.

For code owners to receive review requests, the CODEOWNERS file must be on the base branch of the pull request. For example, if you assign @octocat as the code owner for .js files on the gh-pages branch of your repository, @octocat will receive review requests when a pull request with changes to .js files is opened between the head branch and gh-pages.

CODEOWNERS file size

CODEOWNERS files must be under 3 MB in size. A CODEOWNERS file over this limit will not be loaded, which means that code owner information is not shown and the appropriate code owners will not be requested to review changes in a pull request.

To reduce the size of your CODEOWNERS file, consider using wildcard patterns to consolidate multiple entries into a single entry.

Warning: There are some syntax rules for gitignore files that do not work in CODEOWNERS files:

  • Escaping a pattern starting with # using \ so it is treated as a pattern and not a comment
  • Using ! to negate a pattern
  • Using [ ] to define a character range



Comments

Post a Comment

Popular posts from this blog

GitHub : Troubleshooting

 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++  +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ On GitHub had the following error There isn’t anything to compare. master and feature/godsword are entirely different commit histories. git checkout [BRANCH]    git branch master [BRANCH] -f    git checkout master    git push origin master -f   -- Last command worked   Removing remote repository branch [root@cmptest01-cc dns-new-one]# git push origin --delete feature/godsword To https://github.com/8x8/testing-powerdns-ansible-SRJ.git
Read more

Git Commands : Tags

 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++    +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Topic : Tags :  Reference : https://git-scm.com/book/en/v2/Git-Basics-Tagging >>> Listing Your Tags $ git tag v1.0 v2.0 >>> You can also search for tags that match a particular pattern. The Git source repo, for instance, contains more than 500 tags. If you’re interested only in looking at the 1.8.5 series, you can run this:  $ git tag -l "v1.8.5*" v1.8.5 v1.8.5-rc0 v1.8.5-rc1 v1.8.5-rc2 v1.8.5-rc3 v1.8.5.1 v1.8.5.2 v1.8.5.3 v1.8.5.4 v1.8.5.5 >>> Creating Tags Git supports two types of tags: lightweight and annotated . A lightweight tag is very much like a branch that doesn’t change — it’s just a pointer to a specific commit. Annotated tags, however, are stored as full objects in the Git database. They’re checksummed; contain the tagger name, email, and date; have a tagging message; ...
Read more

GIT - Company

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Large Files error - solution https://docs.github.com/en/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage     +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++  PS C:\Users\sreejith_b\Desktop\OCI_Tech_Hippa> git remote rm origin PS C:\Users\sreejith_b\Desktop\OCI_Tech_Hippa> git remote add origin https://sbalakrishn:SuperBite666#333@github.com/8x8/oci-terraform-hippa-bucket.git PS C:\Users\sreejith_b\Desktop\OCI_Tech_Hippa> git remote rm origin                                             PS C:\Users\sreejith_b\Desktop\OCI_Tech_Hippa> git remote -v                                               ...
Read more