Skip to content

Update geom-text.r #4332

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

Closed
wants to merge 1 commit into from
Closed

Update geom-text.r #4332

wants to merge 1 commit into from

Conversation

larspijnappel
Copy link
Contributor

As proposed, here's a PR for the documentation improvement regarding the unsupported check_overlap argument for geom_label() (#4331).

If this is not sufficient, please advise me on the necessary improvements, as this is my first contribution.

As proposed, here's a PR for the documentation improvement regarding the unsupported `check_overlap` argument for `geom_label()` (#4331).

If this is not sufficient, please advise me on the necessary improvements, as this is my first contribution.
Copy link
Member

@yutannihilation yutannihilation left a comment

Choose a reason for hiding this comment

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

Thanks, a minor comment.

@yutannihilation yutannihilation linked an issue Jan 29, 2021 that may be closed by this pull request
@thomasp85
Copy link
Member

@larspijnappel do you want to finish this off?

@thomasp85 thomasp85 added this to the ggplot2 3.3.4 milestone Mar 25, 2021
@larspijnappel
Copy link
Contributor Author

Hi @thomasp85,

I certainly wish to, but I'm afraid that it's unclear for me what the next-best-action needs to be done (TBH, the GitHub process is a bit overwhelming for me as newbie).

I agree with the feedback from reviewer yutannihilation, but I fail to see if I'm supposed to do something and, if so, how to do that.

Thanks for helping me out.

@thomasp85
Copy link
Member

No problem @larspijnappel — there is definitely a learning curve for all this 🙂

If you look at your own GitHub repository list you can see that you have a fork of ggplot2. This fork contains a branch which is the basis of this PR - you can see the branch name in the top of the PR
image

Any changes to this branch will be reflected in this PR, which is how it is possible to have back-and-forths in a PR with code changes along the way

Are you familiar with working with git from rstudio?

Copy link
Contributor Author

@larspijnappel larspijnappel left a comment

Choose a reason for hiding this comment

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

Yes, I do use git in RStudio, but only for personal use.
Unfortunately, I cannot find my larspijnappel-patch-1 in my GitHub repo anymore..

So, would it best to redo it again: make new fork > apply change > create new pull request?

@thomasp85
Copy link
Member

Yeah, let's start over. I would suggest that you look into the pr_ functions in usethis as these are designed to enforce good practice around creating PRs. See this page on how to get started https://usethis.r-lib.org/articles/articles/pr-functions.html

@larspijnappel
Copy link
Contributor Author

Hi @thomasp85,

Thx very much for the redirection to the very clear written pages of usethis. I've succeeded in completing this new approach and submitted a new PR #4389.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

check_overlap argument not accepted in geom_label()
3 participants