Document code patch maintenance policy

Open
#269 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
documentation

Research direction

The issue names no files, tests, or entry points. Start by reviewing how patches for upstream Drupal core and contrib projects are tracked, then document an agreed maintenance policy and confirm that the policy answers how those patches should be followed.

Written by the indexing model from the issue text.

Description

We want to make it clearer how we keep track of patches for upstream code such as Drupal core and contrib. projects.

Creating this issue to track that and discuss if needed.

Dominant language
No language data
Stars
7
Forks
22
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 localgovdrupal/docs

All issues in localgovdrupal/docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.