Hi, We are currently in the process of migrating the documentation for <code class

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

Legacy documentation about request.js.org HOT 2 OPEN

request commented on August 19, 2024

Legacy documentation

from request.js.org.

Comments (2)

demurgos commented on August 19, 2024

@simov
Could you clarify how you envision the relation between the master and legacy-doc branches ? Here are the three possible ways I see:

Merge legacy-doc right now and delete it, push the new changes to master. (Changes go live as quickly as possible)
Push all the new changes (related to the legacy doc) to legacy-doc and wait until it's stable enough, then merge it to master and delete it, the next changes go to master. (Changes go live once the whole legacy documentation is migrated)
Push new changes to legacy-doc but also perform regularly merges from legacy-doc to master while keeping legacy-doc. The changes continue to go to legacy-doc until the final merge to master after which we delete legacy-doc. (Keep legacy-doc until the end of the migration, but push changes to live from time to time)

from request.js.org.

simov commented on August 19, 2024

Once we have at least all navigation/summary links figured out we can merge to master, effectively publishing the docs to gitbook. Don't worry about missing stuff and TODO's here and there.

Good job on this issue 👍

from request.js.org.

Recommend Projects