-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
add codeowners.md, constributing.md and stale issues action
- Loading branch information
1 parent
e0ce6d7
commit 7f9d334
Showing
3 changed files
with
43 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
* @Adyen/ipp-mobile-ios |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
# Contributing to Adyen | ||
:+1::tada: First off, thanks for taking the time to contribute! :tada::+1: | ||
The following is a set of guidelines for contributing to Adyen and its repositories, which are hosted in the [Adyen Organization](https://github.com/adyen) on GitHub. These are mostly guidelines, not rules. | ||
|
||
## Code of Conduct | ||
This project and everyone participating in it is governed by the [Adyen Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. | ||
|
||
## How to contribute | ||
1. Fork the repository. | ||
2. Create a new branch from the default branch in your repository. This makes it easier for you to keep track of your changes. | ||
3. Make the desired changes to the code. | ||
* If you are adding new functionality or fixing a bug, we recommend you add unit tests that cover it. | ||
4. Push the changes to your fork. | ||
5. Create a pull request to the repository. | ||
6. In your pull request, please describe in detail: | ||
* What problem you’re solving | ||
* Your approach to fixing the problem | ||
* Any tests you wrote | ||
7. Check Allow edits from maintainers. | ||
8. Create the pull request. | ||
9. Ensure that all checks have passed. | ||
|
||
After you create your pull request, one of the code owners will review your code. | ||
We aim to review your request within 2-3 business days. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
name: Github Stale Issues Check | ||
|
||
on: | ||
schedule: | ||
- cron: '59 23 * * *' # Run every day just before midnight | ||
|
||
jobs: | ||
close_stale_prs: | ||
runs-on: ubuntu-latest | ||
steps: | ||
- name: Close stale issues | ||
uses: actions/stale@v9 | ||
with: | ||
any-of-labels: 'Needs more info' | ||
stale-issue-message: 'This issue is stale because it has been open 21 days with no activity. Please comment on this issue otherwise it will be closed in 7 days.' | ||
close-issue-message: 'This issue was closed because it has been stalled for 7 days with no activity.' | ||
days-before-issue-stale: 21 | ||
days-before-issue-close: 7 |