You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
booleanParam(name: 'Run_As_Master_Branch', defaultValue: false, description: 'Allow to run any steps on a PR, some steps normally only run on master branch.')
31
+
booleanParam(name: 'Run_As_Main_Branch', defaultValue: false, description: 'Allow to run any steps on a PR, some steps normally only run on main branch.')
to fix a {issues}1749[possible crash] when polling for central config.
622
622
623
623
@@ -634,7 +634,7 @@ as they are added over time.
634
634
adds a top level `setTransactionOutcome` and `setSpanOutcome` to set
635
635
outcome values for the current active transaction or active span.
636
636
* Limit the `transactionSampleRate` value to 4 decimal places of precision
637
-
according to the shared https://github.com/elastic/apm/blob/master/specs/agents/tracing-sampling.md#transaction_sample_rate-configuration[APM spec]. This ensures that propagated sampling rate
637
+
according to the shared https://github.com/elastic/apm/blob/main/specs/agents/tracing-sampling.md#transaction_sample_rate-configuration[APM spec]. This ensures that propagated sampling rate
638
638
in the `tracestate` header is short and consistent. {pull}1979[#1979]
639
639
640
640
[float]
@@ -700,14 +700,14 @@ slightly to commonalize:
700
700
{pull}1912[#1912]
701
701
702
702
* feat: Add `log_level` central config support. {pull}1908[#1908] +
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,7 +50,7 @@ Once your changes are ready to submit for review:
50
50
3. Rebase your changes
51
51
52
52
Update your local repository with the most recent code from the main repo,
53
-
and rebase your branch on top of the latest master branch.
53
+
and rebase your branch on top of the latest main branch.
54
54
We prefer your initial changes to be squashed into a single commit.
55
55
Later, if we ask you to make changes, add them as separate commits.
56
56
This makes them easier to review.
@@ -137,7 +137,7 @@ npm run backport
137
137
138
138
### Workflow
139
139
140
-
All feature development and most bug fixes hit the master branch first.
140
+
All feature development and most bug fixes hit the main branch first.
141
141
Pull requests should be reviewed by someone with commit access.
142
142
Once approved, the author of the pull request,
143
143
or reviewer if the author does not have commit access,
@@ -172,7 +172,7 @@ If you have access to make releases, the process is as follows:
172
172
173
173
### Current major
174
174
175
-
1. Be sure you have checked out the `master` branch and have pulled latest changes
175
+
1. Be sure you have checked out the `main` branch and have pulled latest changes
176
176
1. Update the version in `package.json` according to the scale of the change. (major, minor or patch)
177
177
1. Update `CHANGELOG.asciidoc`:
178
178
- Change the "Unreleased" section title to:
@@ -183,9 +183,9 @@ If you have access to make releases, the process is as follows:
183
183
- Add missing changelog entries, if any. (Typically commits will include changelog entries in the "Unreleased" section.)
184
184
1. If a major or minor release, update the EOL table in `docs/upgrading.asciidoc`. EOL is 18 months after release date.
185
185
1. Make a PR titled `x.y.z` -- where `x.y.z` is the new version in package.json -- with these changes.
186
-
1. Ensure PR checks pass, then merge to master.
187
-
1. Working on the elastic repo now (not a fork), tag the merged-to-master commit with `git tag vx.y.x && git push origin --tags`. For example: `git tag v1.2.3 && git push origin --tags`.
188
-
1. Reset the latest major branch (currently `3.x`) to point to the current master, e.g. `git branch -f 3.x master && git push origin 3.x`
186
+
1. Ensure PR checks pass, then merge to main.
187
+
1. Working on the elastic repo now (not a fork), tag the merged-to-main commit with `git tag vx.y.x && git push origin --tags`. For example: `git tag v1.2.3 && git push origin --tags`.
188
+
1. Reset the latest major branch (currently `3.x`) to point to the current main, e.g. `git branch -f 3.x main && git push origin 3.x`
189
189
1. Publish to npm with `npm publish`
190
190
191
191
### Past major
@@ -204,4 +204,4 @@ If you have access to make releases, the process is as follows:
204
204
1. Run tests with `npm test`
205
205
1. Push commits and tags upstream with `git push upstream <major_branch> && git push upstream --tags` (and optionally to your own fork as well)
206
206
1. Publish to npm with `npm publish --tag=2x` (where `2x` is the tag for the past major version being published)
207
-
1. Make a PR against `master` containing the updates to `CHANGELOG.asciidoc` so that `master` always contain information about all releases
207
+
1. Make a PR against `main` containing the updates to `CHANGELOG.asciidoc` so that `main` always contain information about all releases
0 commit comments