v2 Upgrade commit detail

Open
#350 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale

Research direction

Start by reviewing the v1 and v2 upgrade commits and the repository history referenced by the issue. Determine whether a repository or commit sequence with more granular v2 changes can be provided; the work is done when the upgrade history is available in a form that supports applying changes incrementally.

Written by the indexing model from the issue text.

Description

@thivy Would you be able to provide a repo with a more detailed commit history for the v2 upgrade? In the case where v1 was in use and heavily modified, it would simplify the upgrade process to be able to have more commit history and apply changes that way rather than all of the v2 changes being applied in the single update commit.

Dominant language
TypeScript
Stars
1.4k
Forks
1.3k
Avg merge
1d 11h
Merged PRs (30d)
1

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 microsoft/azurechat

All issues in microsoft/azurechat

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.