Skip to content

Add new resource sentry_release_deployment #265

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 23 commits into
base: main
Choose a base branch
from
Open
Changes from 1 commit
Commits
Show all changes
23 commits
Select commit Hold shift + click to select a range
2eb3d3d
Add new resource `sentry_release_deployment`
mvantellingen Jan 18, 2023
9c0aa0c
Update sentry/resource_sentry_release_deployment_test.go
mvantellingen Jan 24, 2023
af20a26
Make the fork releasable
mvantellingen Jun 14, 2023
23d67c4
Update README.md
mvantellingen Jun 14, 2023
9c5da47
Simplify reading sentry key
mvantellingen Jul 5, 2023
8af15a4
Update go-sentry to fix issue with project key reading
mvantellingen Jul 5, 2023
7aeee21
Synchronized project metafiles from labd/.github-private
demeyerthom Aug 11, 2023
3889e60
🔄 synced local '.github/' with remote 'projects/go/.github'
labd-project-manager[bot] Sep 1, 2023
c580bd1
🔄 synced local '.github/' with remote 'projects/go-terraform-provider…
labd-project-manager[bot] May 3, 2024
020492b
🔄 synced local '.github/' with remote 'projects/go-terraform-provider…
labd-project-manager[bot] May 7, 2024
fc078a5
🔄 created local '.changie.yaml' from remote 'projects/go-terraform-pr…
labd-project-manager[bot] May 7, 2024
3ee189a
feat: added changie and taskfile
demeyerthom May 7, 2024
f8f9c8e
Merge pull request #1 from labd/feat/changie-taskfile
demeyerthom May 7, 2024
13727ec
🔄 synced local '.github/' with remote 'projects/go-terraform-provider…
labd-project-manager[bot] May 10, 2024
4bbf7d7
🔄 synced local '.github/' with remote 'projects/go-terraform-provider…
labd-project-manager[bot] May 10, 2024
506455e
Update test.yaml
demeyerthom May 17, 2024
502d68d
Release v1.0.3
demeyerthom May 17, 2024
3c306b6
Update v1.0.2.md
demeyerthom May 17, 2024
b26baae
Update CHANGELOG.md
demeyerthom May 17, 2024
e9bc76f
Merge pull request #2 from labd/release/v1.0.3
demeyerthom May 17, 2024
9fba08e
Update release.yaml
demeyerthom May 17, 2024
1b28ec6
🔄 synced local '.github/' with remote 'projects/go-terraform-provider…
labd-project-manager[bot] Aug 2, 2024
11a93c7
🔄 synced local '.github/' with remote 'projects/go-terraform-provider…
labd-project-manager[bot] Mar 7, 2025
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Synchronized project metafiles from labd/.github-private
demeyerthom committed Aug 11, 2023
commit 7aeee218e1a68f23f2f6923df2c698101d56962a
1 change: 1 addition & 0 deletions .github/CODEOWNERS
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
* @labd/go
128 changes: 128 additions & 0 deletions .github/CODE_OF_CONDUCT.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,128 @@
# Contributor Covenant Code of Conduct

## Our Pledge

We as members, contributors, and leaders pledge to make participation in our
community a harassment-free experience for everyone, regardless of age, body
size, visible or invisible disability, ethnicity, sex characteristics, gender
identity and expression, level of experience, education, socio-economic status,
nationality, personal appearance, race, religion, or sexual identity
and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming,
diverse, inclusive, and healthy community.

## Our Standards

Examples of behavior that contributes to a positive environment for our
community include:

* Demonstrating empathy and kindness toward other people
* Being respectful of differing opinions, viewpoints, and experiences
* Giving and gracefully accepting constructive feedback
* Accepting responsibility and apologizing to those affected by our mistakes,
and learning from the experience
* Focusing on what is best not just for us as individuals, but for the
overall community

Examples of unacceptable behavior include:

* The use of sexualized language or imagery, and sexual attention or
advances of any kind
* Trolling, insulting or derogatory comments, and personal or political attacks
* Public or private harassment
* Publishing others' private information, such as a physical or email
address, without their explicit permission
* Other conduct which could reasonably be considered inappropriate in a
professional setting

## Enforcement Responsibilities

Community leaders are responsible for clarifying and enforcing our standards of
acceptable behavior and will take appropriate and fair corrective action in
response to any behavior that they deem inappropriate, threatening, offensive,
or harmful.

Community leaders have the right and responsibility to remove, edit, or reject
comments, commits, code, wiki edits, issues, and other contributions that are
not aligned to this Code of Conduct, and will communicate reasons for moderation
decisions when appropriate.

## Scope

This Code of Conduct applies within all community spaces, and also applies when
an individual is officially representing the community in public spaces.
Examples of representing our community include using an official e-mail address,
posting via an official social media account, or acting as an appointed
representative at an online or offline event.

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported to the community leaders responsible for enforcement at
.
All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the
reporter of any incident.

## Enforcement Guidelines

Community leaders will follow these Community Impact Guidelines in determining
the consequences for any action they deem in violation of this Code of Conduct:

### 1. Correction

**Community Impact**: Use of inappropriate language or other behavior deemed
unprofessional or unwelcome in the community.

**Consequence**: A private, written warning from community leaders, providing
clarity around the nature of the violation and an explanation of why the
behavior was inappropriate. A public apology may be requested.

### 2. Warning

**Community Impact**: A violation through a single incident or series
of actions.

**Consequence**: A warning with consequences for continued behavior. No
interaction with the people involved, including unsolicited interaction with
those enforcing the Code of Conduct, for a specified period of time. This
includes avoiding interactions in community spaces as well as external channels
like social media. Violating these terms may lead to a temporary or
permanent ban.

### 3. Temporary Ban

**Community Impact**: A serious violation of community standards, including
sustained inappropriate behavior.

**Consequence**: A temporary ban from any sort of interaction or public
communication with the community for a specified period of time. No public or
private interaction with the people involved, including unsolicited interaction
with those enforcing the Code of Conduct, is allowed during this period.
Violating these terms may lead to a permanent ban.

### 4. Permanent Ban

**Community Impact**: Demonstrating a pattern of violation of community
standards, including sustained inappropriate behavior, harassment of an
individual, or aggression toward or disparagement of classes of individuals.

**Consequence**: A permanent ban from any sort of public interaction within
the community.

## Attribution

This Code of Conduct is adapted from the [Contributor Covenant][homepage],
version 2.0, available at
https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.

Community Impact Guidelines were inspired by [Mozilla's code of conduct
enforcement ladder](https://github.com/mozilla/diversity).

[homepage]: https://www.contributor-covenant.org

For answers to common questions about this code of conduct, see the FAQ at
https://www.contributor-covenant.org/faq. Translations are available at
https://www.contributor-covenant.org/translations.
2 changes: 2 additions & 0 deletions .github/FUNDING.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
# These are supported funding model platform
github: [labd]
8 changes: 8 additions & 0 deletions .github/ISSUE_TEMPLATE/bug-report.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
---
name: Bug report
about: When you are running into an issue
title: ''
labels: bug, triage
assignees: ''

---
1 change: 1 addition & 0 deletions .github/ISSUE_TEMPLATE/config.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
blank_issues_enabled: false
8 changes: 8 additions & 0 deletions .github/ISSUE_TEMPLATE/feature-request.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
---
name: Feature request
about: When you are missing a specific feature
title: ''
labels: enhancement, triage
assignees: ''

---
8 changes: 8 additions & 0 deletions .github/ISSUE_TEMPLATE/support-request.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
---
name: Support request
about: When you have a generic question
title: ''
labels: question, triage
assignees: ''

---
27 changes: 27 additions & 0 deletions .github/pull-request-template.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
<!--

Describe in detail the changes you are proposing, and the rationale.

-->

<!--

Link all GitHub issues fixed by this PR, and add references to prior related PRs.

-->

Fixes #

### NEW FEATURES | UPGRADE NOTES | ENHANCEMENTS | BUG FIXES | EXPERIMENTS

<!--

Write a short description of your changes. Examples:

- Fixed a bug
- Added a new feature
- Updated documentation

-->

-
27 changes: 27 additions & 0 deletions .github/workflows/triage.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
name: Triage

on:
pull_request:
types:
- opened
issues:
types:
- opened

jobs:
add_to_project:
name: Push issue or PR to board
runs-on: ubuntu-latest
steps:
- name: get app token
id: get-app-token
uses: labd/action-gh-app-token@main
with:
app-id: ${{ secrets.RD_APP_ID }}
private-key: ${{ secrets.RD_APP_PRIVATE_KEY }}
installation-id: ${{ secrets.RD_APP_INSTALLATION_ID }}
- name: set to project board
uses: actions/add-to-project@v0.5.0
with:
project-url: https://github.com/orgs/labd/projects/3
github-token: ${{ steps.get-app-token.outputs.app-token }}