Support markdown comments

Open
#1,149 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, typescript
Domain
ci-cd

Research direction

The issue does not name files, tests, or an entry point. Start by reproducing the linked example and tracing how stale pull-request comments are currently rendered. Done means links and basic Markdown render as Markdown in those comments, with tests covering the behavior.

Written by the indexing model from the issue text.

Description

feature request

Description:
It would be great to have markdown for the message for a stale PRs.
Justification:
This would allow for links and other basic markup to be added which could point to other resources the PR owner should look at to get their PR reviewed.

Are you willing to submit a PR?
Yes - I just want to check it's in scope before going through the effort 😅

Example

CleanShot 2024-03-28 at 13 39 32@2x
Figure: An example of the comments being considered text and not markdown, see https://github.com/SSWConsulting/SSW.GitHub.Template/pull/24

Dominant language
TypeScript
Stars
1.7k
Forks
438
Avg merge
27d 8h
Merged PRs (30d)
1

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 actions/stale

All issues in actions/stale

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.