Move `eng/run.ps1` to `run.ps1` (and other submodule freedoms)
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 431
- Forks
- 44
- Avg merge
- 21h 18m
- Merged PRs (30d)
- 30
Description
We made some choices back when we were using a Git fork that we should revisit now that the upstream code is contained in a submodule:
eng/run.ps1->run.ps1- More generally, we don't have to be concerned about stuffing all of our code into
engto keep it isolated. We can move outeng/doctodoc(ordocs), too.
- More generally, we don't have to be concerned about stuffing all of our code into
- Remove
_foreng/_core,eng/_util- The Go tests traversed the entire Go repository, and
_was how our code was avoiding being tested as if it was part of the standard library. eng/core.- Consider other names that are more descriptive than "core" and "util", and put them in the root of the repo?
- Merging them into one module might help: https://github.com/microsoft/go/issues/402
- The Go tests traversed the entire Go repository, and
- Move
eng/artifactstoartifacts. This is easier to navigate to, and it's more familiar to devs who also work with the .NET source code.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository layout around eng/run.ps1, eng/doc, eng/_core, eng/_util, and eng/artifacts, along with the submodule-related context in the issue. Define the target names and module boundaries before making changes; done means the proposed directories are consistently relocated without breaking the repository’s Go or build workflows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100