microsoft / microsoft/react-native-windows

Update `@rnw-scripts/create-github-releases` to allow for using local GH credentials

Open
#13,903 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area: Release Process enhancement Workstream: ES Compliance SFI
Dominant language
C++
Stars
17.3k
Forks
1.2k
Avg merge
1d 13h
Merged PRs (30d)
33

Description

Summary

The @rnw-scripts/create-github-releases script requires users to specify a GH token/PAT via a command-line argument, and will bail if it's missing.

Instead, if the argument is missing, the script should either use the GH credentials of the current user (if possible) or help the user through getting a PAT (the way when you first clone or push to GH, git takes you through the whole oauth exchange).

Motivation

This script is normally run only in CI as a part of publish, and it has a token. However, sometimes there's problems, and we have to run the script manually. It would be nice if the script could just use the users credentials, or walk the user through authentication to get a PAT, rather than requiring users to go and make a PAT manually correctly by themselves.

Basic Example

No response

Open Questions

No response

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.

Research direction

Start at the @rnw-scripts/create-github-releases entry point and inspect how it currently handles a missing command-line token. Compare available local GitHub authentication options with the requested interactive PAT flow; done means manual runs can authenticate without requiring users to create and pass a token themselves, while CI token usage remains supported.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.