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

Add cluster doc code examples #2461

Merged
merged 1 commit into from
Feb 28, 2024
Merged

Conversation

anniegale9538
Copy link
Contributor

Hello!

I'm adding cluster doc code examples per #2429

Thanks, @pquentin you're a hero!

cc @stefnestor

Copy link

cla-checker-service bot commented Feb 24, 2024

💚 CLA has been signed

Copy link

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

@pquentin pquentin changed the title adding cluster doc code examples Add cluster doc code examples Feb 25, 2024
Copy link
Member

@pquentin pquentin left a comment

Choose a reason for hiding this comment

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

This looks great, thank you! And a great start towards adding more cluster docs examples. And of course, you're the hero, not me.

The only issue is the CLA check. You don't have to sign one as an Elastic employee, but for this to work you have to use your elastic.co address, which you are not doing, see here: https://github.com/elastic/elasticsearch-py/commit/2bcbf9a20a34e2afef65b4621924d97cdd49cd31.patch. You'll have to amend your commit to include the correct email and force push, I'm happy to explain more if you'd like.

@stefnestor
Copy link
Contributor

👋 @pquentin, thanks 💚! Could you kindly explain a bit more 🙏?

I think I got us close but not quite and I'm not sure how to fix. Annie was moving between two Github accounts (personal @scranberryjam to Elastician @anniegale9538 ) and signed the CLA agreement under both Github usernames (though the second one which we believe is attached to this PR - since we were doing the commit together zooming sharing her work computer's screen - was CLA-signed after the above message popped up).

Could the problem be I missed setting Annie's Git PR email address which is what's needed to connect to the CLA agreement? E.g. Git Blame exposing email via -e doesn't list Annie's personal/work email 😕

elasticsearch-py$ git branch
* (HEAD detached at upstream/annie/adding_to_files_to_generate)

elasticsearch-py$ git blame -e docs/examples/1cecd4d87a92427175157d41859df2af.asciidoc
2bcbf9a20 (<[email protected]> 2024-02-24 11:35:45 -0700  1) // cluster/allocation-explain.asciidoc:10

@anniegale9538
Copy link
Contributor Author

@stefnestor @pquentin I am wondering if it happened because I had "Keep my email addresses private" marked under my email on my anniegale9538 github account 😞 I unclicked that and am verifying my user.email now!

@pquentin
Copy link
Member

Sorry for the delay! Indeed the issue here is the email in the git commit, not the GitHub user. You're going to have to amend the commit to include the correct email, and then do a force push:

git commit --amend --author="Annie Hansen <[email protected]>"
git push --force-with-lease

And to be sure you don't hit this issue for your next PRs, make sure to fix the email globally too:

git config --global user.name "Annie Hansen"
git config --global user.email "[email protected]"

https://www.git-tower.com/learn/git/faq/change-author-name-email is a good reference on that topic.

Hope that helps! If not, I'm also happy to assist more.

@anniegale9538 anniegale9538 force-pushed the annie/adding_to_files_to_generate branch from 2bcbf9a to 1a49450 Compare February 28, 2024 01:58
@anniegale9538
Copy link
Contributor Author

anniegale9538 commented Feb 28, 2024 via email

Copy link
Member

@pquentin pquentin 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! LGTM.

@pquentin pquentin merged commit 74a531c into main Feb 28, 2024
18 checks passed
@pquentin pquentin deleted the annie/adding_to_files_to_generate branch February 28, 2024 08:26
github-actions bot pushed a commit that referenced this pull request Feb 28, 2024
pquentin pushed a commit that referenced this pull request Feb 28, 2024
iuliaferoli pushed a commit to iuliaferoli/elasticsearch-py that referenced this pull request Mar 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants