From 2fc2ccf4fadbd11d8079e733b576f84309de99d4 Mon Sep 17 00:00:00 2001 From: zer0Kerbal <39887717+zer0Kerbal@users.noreply.github.com> Date: Fri, 24 Jun 2022 22:41:22 -0500 Subject: [PATCH] Delete settings.yml --- .github/settings.yml | 243 ------------------------------------------- 1 file changed, 243 deletions(-) delete mode 100644 .github/settings.yml diff --git a/.github/settings.yml b/.github/settings.yml deleted file mode 100644 index 043113de..00000000 --- a/.github/settings.yml +++ /dev/null @@ -1,243 +0,0 @@ -# settings.yml 1.0.9.4 -# this file: CC BY-ND 4.0 -# zer0Kerbal -# created 01 Jan 2022 -# updated 03 Jun 2022 -# These settings are synced to GitHub by https://probot.github.io/apps/settings/ -# See https://docs.github.com/en/rest/reference/repos#update-a-repository for all available settings. - -repository: - # See https://docs.github.com/en/rest/reference/repos#update-a-repository for all available settings. - - # The name of the repository. Changing this will rename the repository - name: SimpleConstruction - - # A short description of the repository that will show up on GitHub - description: "Provides simple craft building capability in flight mode to stock parts for Kerbal Space Program." - - # A URL with more information about the repository - homepage: https://forum.kerbalspaceprogram.com/index.php?/topic/191424-* - - # A comma-separated list of topics to set on the repository - topics: rocketparts,resource,isru,simple,simpleconstruction,scon,launchpad,el,extraplanetarylaunchpads, vessel-assembly, kerbal,kerbalspaceprogram,ksp,ksp-mods,ksp-parts,kerbal-space,kerbal-space-program,kerbal-mods,zedk,taniwha - -# Labels: define labels for Issues and Pull Requests -labels: - - name: bug 🐛 - color: CC0000 - description: An issue with the system. Something isn't working... KSC... we have an error code - - - name: "help wanted" - color: 008672 - description: "assistance, help, input solicited" - - - name: discussion - color: 6495ED - description: "duplicated issue - it happens" - - - name: duplicate - color: FFFFF0 - description: "duplicated issue - it happens" - - - name: FAQ - color: 78A1A5 - description: "Frequently Asked Question" - - - name: "semantic: adoption" - # include the old name to rename an existing label - oldname: adoption - color: BADA55 - description: relating to adoption - - - name: "semantic: release" - color: 00FF00 - description: release - - - name: "semantic: prerelease" - color: 00FF00 - description: prerelase - - - name: "semantic: beta" - color: 00FF00 - description: beta - - - name: "semantic: alpha" - color: 00FF00 - description: alpha - - - name: "issue: text" - color: FBCA04 - description: issue type - - - name: "issue: compatibility/patch" - color: CC0DEB - description: issue type - - - name: "issue: model" - color: FBCA04 - description: issue type - - - name: "issue: texture" - color: FBCA04 - description: issue type - - - name: "issue: sound" - color: FBCA04 - description: issue type - - - name: "issue: config" - color: FBCA04 - description: issue type - - - name: "issue: code" - color: FBCA04 - description: issue type - - - name: "issue: documentation" - color: FBCA04 - description: issue type - - - name: "issue: relationship" - color: FBCA04 - description: issue type - - - name: "issue: license" - color: FBCA04 - description: having to do with license/licensing - - - name: "issue: image" - color: FBCA04 - description: deals with images and imgbot - - - name: "issue: install" - color: FBCA04 - description: issue type - - - name: "issue: other" - color: FBCA04 - description: issue type - - - name: "issue: external" - color: FBCA04 - description: issue originates from external sources - - - name: "type: localization" - oldname: localization - # include the old name to rename an existing label - color: FFFFF0 - description: related to localization and translations - - - name: "type: infrastructure" - color: ffdda8 - description: improvements or additions to project infrastructure - - - name: "type: automation" - color: fbca04 - description: issues for automation actions - - - name: "type: fix" - color: 91ca55 - description: Iterations on existing features or infrastructure. - - - name: "type: testing" - color: fbca04 - description: Related to testing. - - - name: "type: chore" - color: fef2c0 - description: Converting measurements, reorganizing folder structure, and other necessary (but less impactful) tasks. - - - name: "type: discussion" - oldname: discussion - color: d4c5f9 - description: Questions, queries, posers, proposals and info that requires discussion. - - - name: "type: docs" - color: fef2c0 - description: Related to documentation and information. - - - name: "type: pages" - color: fef2c0 - description: Related to GitHub pages documentation and information. - - - name: "type: enhancement" - oldname: "Mod-enhancement" - # include the old name to rename an existing label - color: 5ebeff - description: Requested functionality, features, pages, workflows, endpoints, etc. - - - name: "type: feature" - oldname: "Mod-feature" - # include the old name to rename an existing label - description: Brand new functionality, features, pages, workflows, endpoints, etc. - - - name: "type: request" - oldname: "Mod-request" - # include the old name to rename an existing label - color: 5ebeff - description: Requested functionality, features, pages, workflows, endpoints, etc. - - - name: "type: archive" - color: FFFFF0 - description: archive - - - name: "type: upstream" - oldname: "upstream" - # include the old name to rename an existing label - color: FFFFF0 - description: upstream or side stream - - - name: "type: pull request" - oldname: "pull request" - color: FFFFF0 - description: upstream or side stream - - - name: "work: choatic" - color: FBCA04 - description: The situation is chaotic, novel practices used. - - - name: "work: complex" - color: d4c5f9 - description: The situation is complex, emergent practices used. - - - name: "work: complicated" - color: ffb8c6 - description: The situation is complicated, good practices used. - - - name: "work: obvious" - color: 91ca55 - description: The situation is obvious, best practices used. - - - name: "state: approved" - color: 91ca55 - description: Approved to proceed. - - - name: "state: blocked" - color: d73a4a - description: Something is blocking action. - - - name: "state: pending" - color: fbca04 - description: Taking action, but need a few things to happen first. A feature that needs dependencies merged, or a bug that needs further data. - - - name: "state: inactive" - color: e6e6e6 - description: No action needed or possible. The issue is either fixed, addressed better by other issues, or just out of product scope. - - - name: "state: planning" - color: FFFF00 - description: - - - name: "state: won't fix" - color: e6e6e6 - description: No action will be taken at this time - -# Milestones: define milestones for Issues and Pull Requests -# milestones: -# - title: 4.0.99.1-prerelease -# description: progress toward 4.0.99.1-prerelease -# state: open - -# - title: Localization - Master -# description: progress toward total localization -# state: open