Skip to content

Commit 1401d4d

Browse files
committed
Moving to main
1 parent b1b960e commit 1401d4d

File tree

6 files changed

+24
-25
lines changed

6 files changed

+24
-25
lines changed

.github/workflows/coveralls.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
1-
on: ["pull_request"]
2-
31
name: Coveralls
42

3+
on: ["pull_request"]
4+
55
jobs:
66

77
build:

.github/workflows/models.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ jobs:
2424
token: ${{ secrets.ADYEN_AUTOMATION_BOT_ACCESS_TOKEN }}
2525
committer: ${{ secrets.ADYEN_AUTOMATION_BOT_EMAIL }}
2626
author: ${{ secrets.ADYEN_AUTOMATION_BOT_EMAIL }}
27-
base: develop
27+
base: main
2828
branch: automation/models
2929
title: ${{ steps.vars.outputs.pr_title }}
3030
body: ${{ steps.vars.outputs.pr_body }}

.github/workflows/release.yml

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,4 +30,3 @@ jobs:
3030
develop-branch: main
3131
version-files: package.json
3232
pre-release: ${{ inputs.pre-release || false }}
33-
separator: .pre.beta

.github/workflows/services.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ jobs:
2424
token: ${{ secrets.ADYEN_AUTOMATION_BOT_ACCESS_TOKEN }}
2525
committer: ${{ secrets.ADYEN_AUTOMATION_BOT_EMAIL }}
2626
author: ${{ secrets.ADYEN_AUTOMATION_BOT_EMAIL }}
27-
base: develop
27+
base: main
2828
branch: automation/services
2929
title: ${{ steps.vars.outputs.pr_title }}
3030
body: ${{ steps.vars.outputs.pr_body }}

CONTRIBUTING.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@
33
## How to contribute step-by-step
44

55
1. Fork the `Adyen/adyen-node-api-library` repository.
6-
2. Create a new branch from `develop` in your fork. This makes it easier for you to keep track of your changes.
6+
2. Create a new branch from `main` in your fork. This makes it easier for you to keep track of your changes.
77
3. Make the desired changes to the code.
88
* If you are adding new functionality or fixing a bug, we recommend you add unit tests that cover it.
99
4. Push the changes to your fork.

0 commit comments

Comments
 (0)