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

Update long-email.md #39

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update long-email.md #39

wants to merge 1 commit into from

Conversation

akhaiat2
Copy link

No description provided.

Copy link
Member

@luizaandrade luizaandrade left a comment

Choose a reason for hiding this comment

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

Thanks, @akhaiat2.

I think the point of the issue was to make the e-mail less wordy while still maintaining the key points.

(No need to actually do this, I just wanted to use the "Request changes" option so we have an example in the repo.)

There are two good practices there could be added to this PR:

  1. Including a message in the Pull Request explaining what you did and why. You can, for example, link to the original issue by making the PR message simply "Fix issue Shorten e-mail #22". This will link from the issue to the PR and vice-versa. It will also close the issue when the PR is merged to main. (Here's the documentation on this linking practice)

  2. Adding a reviewer to the PR (on the top right corner), so someone is notified that it has been open.

Base automatically changed from develop to main August 8, 2023 15:10
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.

2 participants