Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Replying to GitHub notifications

Open
#13,402 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
52/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github, javascript
Domain
full-stack

Research direction

No file or test is named. Start by tracing how replies build quoted content, including the Links section and HTML/plain-text selection, then compare the generated reply with GitHub's quoted-reply requirements. Done means GitHub notifications no longer include the original notification as posted content while ordinary replies retain their intended quoting behavior.

Written by the indexing model from the issue text.

Description

1. to develop bug
Is your feature request related to a problem? Please describe.

When replying to email notifications from GitHub, the original notification gets posted along with the new message.

GitHub tries to remove quoted replies to avoid this, but it seems like the format Nextcloud Mail produces is not compatible.

Describe the solution you'd like

Adjust the quote format to be compatible with GitHub's parser.

I think the problems are:

  • This Links: section being created below the quoted content
  • The editor using HTML because the notification was HTML, despite me having plain text set as preferred
Describe alternatives you've considered

Detect Reply-to: *@reply.github.com, List-ID: * <*.github.com>, or some other indicator, and automatically disable sending the quote as a special case.

Additional context
Image
Dominant language
JavaScript
Stars
1k
Forks
363
Avg merge
1d 18h
Merged PRs (30d)
81

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nextcloud/mail

All issues in nextcloud/mail

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.