Pete Gonzalez

It's still not resolved? Did they reply to you?

> Unfortunately I never heard back :( @apostolisms Are you able to escalate this somehow to the CLA bot owners? @dfee is trying to contribute to Rush Stack, but the...

Thanks for making a PR! 😁 Could you add a test case to the **rushstack\build-tests\api-extractor-scenarios** folder? (The test cases get registered in [rushstack\build-tests\api-extractor-scenarios\config\build-config.json](https://github.com/microsoft/rushstack/blob/a7546938f9745291b455546a3e15bb94661c727c/build-tests/api-extractor-scenarios/config/build-config.json).)

> I am getting a build failure on Windows in `node-core-library`. blocking `api-extractor-scenarios` from building. > > I'm just building using `rush update` then `rush build` in Windows PowerShell, and...

> I don't know if there are other special instructions for building on windows because I can't find documentation on the build process. API Extractor docs are [here](https://api-extractor.com/pages/contributing/building/). General repo...

@willmtemple Following up -- are you still working on this PR? Do you need anything else from us?

In my experience, **tsconfig.json** paths seem to be a poor practice for large scale code bases, due to the following chain of reasoning: - If you make a library package...

> > I can help with PR if we need to update/refresh something @zouxuoz are you still available to help? We can merge this PR if someone can fix the...

Can we apply this to Heft? That might be even more interesting.

> Dealing with the same issue and it's breaking my integration with docusaurus. The `` comments are an escaping mechanism. The official escaping mechanism of CommonMark is the backslash `\`,...