microsoft / microsoft/pxt-microbit

Repo's break after changing between private and public

Open
#4,133 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

GitHubIntegration P2
Dominant language
TypeScript
Stars
804
Forks
721
Avg merge
2d 9h
Merged PRs (30d)
2

Description

We have had two repo that have had an issue between changing the repo from public to private (for development work) and then back to public. The issue one repo was posted on the forum (link below) about blocks not being pulled into tutorials correctly. When changes had been done, it would still not update and seem to pull in old versions of the code.

https://forum.makecode.com/t/tutorial-tool-blocks-not-appearing/8216?u=philatkitronik

After creating a new repo and copying the same code over into new files, the tutorials blocks all work fine.

The other repo that has had an issues, after doing the same switch between public > private > public, was unable to commit any work via the online integration. This resulting having to create a new repo for this extenstion

The link to the two repo's are

https://github.com/KitronikLtd/pxt-kitronik-labbit

https://github.com/KitronikLtd/FAULTYpxt-kitronik-air-quality

@pelikhan @martinwork @abchatra @AlasdairAtKitronik

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 by reproducing the public-to-private-to-public transition with the linked Kitronik repositories. Compare tutorial block loading and online integration commits before and after the visibility change; done means both repositories continue loading current tutorial blocks and accepting commits without requiring a new repository.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
developer-experience
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.