Git Product home page Git Product logo

repo-management's Introduction

repo-management

OpenCollective OpenCollective License

A repo of helpful things for managing the many repos in sous-chefs org (easily updatable to use in other orgs)

Usage

Scripts

Most scripts require you be in a directory containing all the repos you'd like to act on, for example:

/home/sous-chefs/
  aptly/
  apache2/
  ...
Script Name Description Usage
add_codeowners_if_not_present.rb Adds/updates a CODEOWNERS file with the repo name as team name ruby add_codeowners_if_not_present.rb <GITHUB_USERNAME> <GITHUB_PASSWORD_OR_TOKEN>
clone_all_repos_in_org.sh clones all repos in github org clone_all_repos_in_org.sh
git_branch_commit_push.sh Pulls master, then checks out a new branch, commits and pushes git_branch_commit_push.sh <path to git ssh key> <branch name> <commit message>
open_pull_requests.rb Opens a pull request `ruby open_pull_requests.rb <user_name> <token
update_labels.sh Removes the Dangerfile PR label check update_labels.sh
watch_repos.rb Watches all repos in org ruby watch_repos.rb <GITHUB_USERNAME> <GITHUB_PASSWORD_OR_TOKEN>

Standard Files

Each folder under standardfiles/ represents a standard file structure we want in a certian type of repository, such as a cookbook.

Automated tools ensure these are kept in sync.

Contributors

This project exists thanks to all the people who contribute.

Backers

Thank you to all our backers!

https://opencollective.com/sous-chefs#backers

Sponsors

Support this project by becoming a sponsor. Your logo will show up here with a link to your website.

https://opencollective.com/sous-chefs/sponsor/0/website https://opencollective.com/sous-chefs/sponsor/1/website https://opencollective.com/sous-chefs/sponsor/2/website https://opencollective.com/sous-chefs/sponsor/3/website https://opencollective.com/sous-chefs/sponsor/4/website https://opencollective.com/sous-chefs/sponsor/5/website https://opencollective.com/sous-chefs/sponsor/6/website https://opencollective.com/sous-chefs/sponsor/7/website https://opencollective.com/sous-chefs/sponsor/8/website https://opencollective.com/sous-chefs/sponsor/9/website

repo-management's People

Contributors

arsh25 avatar axelrtgs avatar bmhughes avatar damacus avatar johnroesler avatar josephholsten avatar mbaitelman avatar onlyhavecans avatar powerschill avatar ramereth avatar stromweld avatar tas50 avatar xorima avatar xorimabot avatar

Stargazers

 avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

repo-management's Issues

Run latest cookstyle

๐Ÿ—ฃ๏ธ Foreword

Thank for taking the time to fill this bug report fully. Without it we may not be able to fix the bug, and the issue may be closed without resolution.

๐Ÿ‘ป Brief Description

Chef have released updated cookstyle rules, we should therefore run the auto fix against the cookbook

  1. Ensure you are on the latest stable chef-workstation
  2. Run cookstyle -a

Issue sprouted from sous-chefs/meta/issues/111. If not applicable then issue should be closed.

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

This repository currently has no open or pending branches.

Detected dependencies

None detected


  • Check this box to trigger a request for Renovate to run again on this repository

Update Changelog

๐Ÿ—ฃ๏ธ Foreword

Thank for taking the time to fill this bug report fully. Without it we may not be able to fix the bug, and the issue may be closed without resolution.

๐Ÿ‘ป Brief Description

Update all CHANGELOGs to follow standard defined at https://keepachangelog.com/

Issue sprouted from sous-chefs/meta/issues/101. If not applicable then issue should be closed.

Standardise repository files

Currently we have different files in each cookbook, we should create a default list of files to be included in all repositories (or at least all cookbook repositories)

If we use apache2 as the base (It has a complete set of files imo) there is a need to review the following files:

  • All documents should be generic so copy and paste between repos is easy
  • Contributing, talks about not changing the changelog, lwrps and recipes
  • Upgrading, should we have this included even if it is blank to encourage people to fill out for breaking changes? If we have a label of breaking change should we have danger fail if this file has not been changed?

Files I feel we should include in all repositories:

  • .gitignore
  • Berksfile (Should we also include a Policyfile?)
  • CHANGELOG.md
  • chefignore
  • CODE_OF_CONDUCT.md
  • CONTRIBUTING.md
  • Dangerfile
  • LICENSE
  • README.md
  • TESTING.md
  • UPGRADING.md

This issue is as much to start a conversation around this topic :)

Would it also be good to include a security md file for responsible disclosure issues

Remove .rubocop.yml with Dangerfile

๐Ÿ—ฃ๏ธ Foreword

Thank for taking the time to fill this bug report fully. Without it we may not be able to fix the bug, and the issue may be closed without resolution.

๐Ÿ‘ป Brief Description

If the only thing in the .rubocop/yml is Dangerfile
Run the latest cookstyle
Remove .rubpopo.yml

Issue sprouted from sous-chefs/meta/issues/108. If not applicable then issue should be closed.

Labels

While we have new standardised labels thanks to @damacus I would like to propose a few additional labels:

name purpose
Release To show us this is for release, could enable us to have some fancy dangerfile checks in future, such as to warn if metadata is changed without a release label
Breaking Change When we merge it is good to know if we need to do a major iteration or not
Documentation when we are lacking documentation
Support When a user has a general question not related to a software defect

Also note labels have not been installed on sc-nxlog and unifi, these are forks though so I think we should unfork these?

Update builds to be parallel

๐Ÿ—ฃ๏ธ Foreword

Thank for taking the time to fill this bug report fully. Without it we may not be able to fix the bug, and the issue may be closed without resolution.

๐Ÿ‘ป Brief Description

As part of our build process we should build each possible operating system separately

  1. Ensure you have dokken setup and working:
  2. dokken: aliased to KITCHEN_LOCAL_YAML=kitchen.dokken.yml kitchen
  3. run dokken list, you should see a list of builds with dokken as the provider
  4. download: https://github.com/sous-chefs/repo-management/blob/master/scripts/circleci_maker.rb and make this executable
  5. run: dokken list -j | ./circleci_maker.rb > .circleci/config.yml

Issue sprouted from sous-chefs/meta/issues/112. If not applicable then issue should be closed.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.