Skip to content
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

docs: copypaste docs bout __process_pid__ label #2988

Merged
merged 1 commit into from
Feb 8, 2024

Conversation

korniltsev
Copy link
Collaborator

@korniltsev korniltsev requested review from a team as code owners February 6, 2024 05:18
Copy link
Contributor

@Rperry2174 Rperry2174 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm

@knylander-grafana knylander-grafana added the type/docs Improvements for doc docs. Used by Docs team for project management label Feb 6, 2024
Copy link
Contributor

@knylander-grafana knylander-grafana left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for updating the docs.

@korniltsev korniltsev merged commit b95e97d into main Feb 8, 2024
20 checks passed
@korniltsev korniltsev deleted the ebpf-docs-pid-update branch February 8, 2024 06:54
@knylander-grafana knylander-grafana added the backport release/v1.4 This label will backport a merged PR to the release/v1.4 branch label Feb 29, 2024
github-actions bot pushed a commit that referenced this pull request Feb 29, 2024
Copy link
Contributor

The backport to release/v1.4 failed:

Validation Failed: "Could not resolve to a node with the global id of 'T_kwDOAG3Mbc4AczmP'."

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-2988-to-release/v1.4 origin/release/v1.4
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x b95e97de36299ab6408c51625bba2dde63423f42

When the conflicts are resolved, stage and commit the changes:

git add . && git cherry-pick --continue

If you have the GitHub CLI installed:

# Push the branch to GitHub:
git push --set-upstream origin backport-2988-to-release/v1.4
# Create the PR body template
PR_BODY=$(gh pr view 2988 --json body --template 'Backport b95e97de36299ab6408c51625bba2dde63423f42 from #2988{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title "[release/v1.4] docs: copypaste docs bout __process_pid__ label" --body-file - --label "type/docs" --label "backport" --base release/v1.4 --milestone release/v1.4 --web

Or, if you don't have the GitHub CLI installed (we recommend you install it!):

# Push the branch to GitHub:
git push --set-upstream origin backport-2988-to-release/v1.4

# Create a pull request where the `base` branch is `release/v1.4` and the `compare`/`head` branch is `backport-2988-to-release/v1.4`.

# Remove the local backport branch
git switch main
git branch -D backport-2988-to-release/v1.4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport release/v1.4 This label will backport a merged PR to the release/v1.4 branch backport-failed type/docs Improvements for doc docs. Used by Docs team for project management
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants