Skip to content

Commit

Permalink
Merge pull request #75 from himanshu-kun/update-pr-template
Browse files Browse the repository at this point in the history
Updated PR , issue template and slack channel
  • Loading branch information
unmarshall authored Jan 27, 2023
2 parents 6923600 + c85b24c commit 1d08025
Show file tree
Hide file tree
Showing 5 changed files with 65 additions and 32 deletions.
13 changes: 9 additions & 4 deletions .ci/pipeline_definitions
Original file line number Diff line number Diff line change
Expand Up @@ -17,14 +17,14 @@ dependency-watchdog:
- linux/arm64
dockerimages:
dependency-watchdog:
registry: 'gcr-readwrite'
image: 'eu.gcr.io/gardener-project/gardener/dependency-watchdog'
dockerfile: 'Dockerfile'
inputs:
repos:
source: ~
steps:
build: ~
registry: 'gcr-readwrite'
image: 'eu.gcr.io/gardener-project/gardener/dependency-watchdog'
dockerfile: 'Dockerfile'
steps:
check:
image: 'golang:1.19.4'
Expand All @@ -33,7 +33,6 @@ dependency-watchdog:
build:
image: 'golang:1.19.4'
output_dir: 'binary'

jobs:
head-update:
traits:
Expand All @@ -45,4 +44,10 @@ dependency-watchdog:
preprocess: 'finalize'
release:
nextversion: 'bump_minor'
slack:
default_channel: 'internal_scp_workspace'
channel_cfgs:
internal_scp_workspace:
channel_name: 'C03D20YPU2K' # gardener-dwd
slack_cfg_name: 'scp_workspace'
component_descriptor: ~
37 changes: 26 additions & 11 deletions .github/ISSUE_TEMPLATE/bug_report.md
Original file line number Diff line number Diff line change
@@ -1,22 +1,37 @@
---
name: Bug report
about: Create a report to help us improve
title: "[BUG]"
name: Bug Report
about: Report a bug encountered while operating DWD
labels: kind/bug
assignees: ''

---

**Describe the bug:**
A clear and concise description of what the bug is.
**How to categorize this issue?**
<!--
Please select area, kind, and priority for this issue. This helps the community categorizing it.
Replace below TODOs or exchange the existing identifiers with those that fit best in your opinion.
If multiple identifiers make sense you can also state the commands multiple times, e.g.
/area control-plane
/area auto-scaling
...
**Expected behaviour:**
A clear and concise description of what you expected to happen.
"/area" identifiers: audit-logging|auto-scaling|backup|certification|control-plane-migration|control-plane|cost|delivery|dev-productivity|disaster-recovery|documentation|high-availability|logging|metering|monitoring|networking|open-source|ops-productivity|os|performance|quality|robustness|scalability|security|storage|testing|usability|user-management
"/kind" identifiers: api-change|bug|cleanup|discussion|enhancement|epic|impediment|poc|post-mortem|question|regression|task|technical-debt|test
"/priority" identifiers: 1|2|3|4|5 (ordered from greatest to least)
-->
/area TODO
/kind bug
/priority 3

**How To Reproduce (as minimally and precisely as possible):**
**What happened**:

**Logs:**
**What you expected to happen**:

**Screenshots (if applicable):**
**How to reproduce it (as minimally and precisely as possible)**:

**Anything else we need to know?**:

**Environment**:

- Kubernetes version (use `kubectl version`):
- Cloud provider or hardware configuration:
- Others:
27 changes: 27 additions & 0 deletions .github/ISSUE_TEMPLATE/enhancement_request.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
---
name: Enhancement Request
about: Suggest an enhancement to the Gardener/DWD project
labels: kind/enhancement

---

**How to categorize this issue?**
<!--
Please select area, kind, and priority for this issue. This helps the community categorizing it.
Replace below TODOs or exchange the existing identifiers with those that fit best in your opinion.
If multiple identifiers make sense you can also state the commands multiple times, e.g.
/area control-plane
/area auto-scaling
...
"/area" identifiers: audit-logging|auto-scaling|backup|certification|control-plane-migration|control-plane|cost|delivery|dev-productivity|disaster-recovery|documentation|high-availability|logging|metering|monitoring|networking|open-source|ops-productivity|os|performance|quality|robustness|scalability|security|storage|testing|usability|user-management
"/kind" identifiers: api-change|bug|cleanup|discussion|enhancement|epic|impediment|poc|post-mortem|question|regression|task|technical-debt|test
"/priority" identifiers: 1|2|3|4|5 (ordered from greatest to least)
-->
/area TODO
/kind enhancement
/priority 3

**What would you like to be added**:

**Why is this needed**:
14 changes: 0 additions & 14 deletions .github/ISSUE_TEMPLATE/feature_request.md

This file was deleted.

6 changes: 3 additions & 3 deletions .github/pull_request_template.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,9 +12,9 @@ Fixes #
Format of block header: <category> <target_group>
Possible values:
- category: improvement|noteworthy
- target_group: user|operator
- category: breaking|feature|bugfix|doc|other
- target_group: user|operator|developer|dependency
-->
```improvement operator
```other operator
```

0 comments on commit 1d08025

Please sign in to comment.