Rename released module to Microsoft.PowerShell.PSReadline for next major version

Open
#3,787 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
cli, release

Research direction

No files, tests, or entry points are named. Start by locating the module metadata and release/version configuration, then trace references to the current module name. Done means the module uses Microsoft.PowerShell.PSReadline for the next major version without leaving inconsistent references.

Written by the indexing model from the issue text.

Description

Issue-Enhancement
Prerequisites
  • Write a descriptive title.
Description of the new feature/enhancement

This is something that is happening with other modules that started out as non-team work and have then jumped into the product, including PSResourceGet, ThreadJob and others.

This is to align with that expectation

cc @daxian-dbw @StevenBucher98

Proposed technical implementation details (optional)

No response

Dominant language
C#
Stars
4.4k
Forks
341
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 PowerShell/PSReadLine

All issues in PowerShell/PSReadLine

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.