Skip to content

History / How to Contribute

Revisions

  • Suggest `git clean -xfd` for failed build (#232)

    @gjsjohnmurray gjsjohnmurray committed Aug 5, 2022
    6768b0c

  • Replaced wrong url in HOW-TO-CONTRIBUTE.md (#228) * Fix #227 * Fix link Co-authored-by: Daniel Imms <2193314+Tyriar@users.noreply.github.com>

    @dydFreeman dydFreeman committed Aug 3, 2022
    07ba578

  • Update node version

    @lramos15 lramos15 committed May 11, 2022
    44a20c8

  • Updated How to Contribute (markdown)

    @aeschli aeschli committed Mar 25, 2022
    b9550e6

  • Update the Node.js version requirements (#213)

    @ronsmith ronsmith committed Mar 14, 2022
    ac9e53e

  • Updated How to Contribute (markdown)

    @joaomoreno joaomoreno committed Mar 7, 2022
    9d05b88

  • Updated How to Contribute (markdown)

    @joaomoreno joaomoreno committed Mar 7, 2022
    1cc604e

  • Updated How to Contribute (markdown)

    @joaomoreno joaomoreno committed Mar 7, 2022
    b4763f6

  • Merge remote-tracking branch 'vsc/master'

    @Tyriar Tyriar committed Feb 22, 2022
    09858dd

  • Update on how to run the web bits

    @aeschli aeschli committed Feb 1, 2022
    666cfba

  • Update How-to-Contribute.md (Debugging) Update for the Debugging (Using VS Code) section. The Debugger for Chrome extension is no longer needed for debugging as Visual Studio Code now has a bundled JavaScript Debugger. See https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome for further infromation.

    @cwr73 cwr73 committed Dec 24, 2021
    0471756

  • Updated How to Contribute (markdown)

    @dbaeumer dbaeumer committed Dec 1, 2021
    3d8d6a3

  • Updated How to Contribute (markdown)

    @dbaeumer dbaeumer committed Dec 1, 2021
    6859c8e

  • Updated How to Contribute (markdown)

    @dbaeumer dbaeumer committed Dec 1, 2021
    55f0784

  • Add warning about building in a terminal

    hata committed Nov 29, 2021
    046dcdb

  • Add more detailed explanation for incremental builder

    hata committed Nov 25, 2021
    78f5acc

  • Updated How to Contribute (markdown)

    @TylerLeonhardt TylerLeonhardt committed Oct 12, 2021
    f1b70b7

  • Updated How to Contribute (markdown)

    @TylerLeonhardt TylerLeonhardt committed Oct 12, 2021
    7439b92

  • update example Refs https://github.com/microsoft/vscode/issues/131074

    @deepak1556 deepak1556 committed Sep 8, 2021
    7585a34

  • Merge remote-tracking branch 'upstream/master' into HEAD

    VSO-Build-Agent committed Sep 7, 2021
    a45e1b0

  • Mention vs2019_install for microsoft/vscode#131074

    @rzhao271 rzhao271 committed Sep 7, 2021
    4eac4c5

  • Update How-to-Contribute.md fix typo

    @deontic deontic committed Sep 6, 2021
    a6f0cbb

  • Update How-to-Contribute.md

    @Tyriar Tyriar committed Aug 11, 2021
    f84d114

  • Clarify packaging instructions It wasn't clear that I couldn't just run `gulp vscode-linux-x64`. I mean I guess that works if you have gulp installed globally but it isn't in the dev container. `yarn run gulp` works though.

    @Timmmm Timmmm committed Aug 11, 2021
    4b2c810

  • minor grammatical changes

    @blueputty01 blueputty01 committed Jul 17, 2021
    b687df0

  • Merge remote-tracking branch 'upstream/master'

    @Tyriar Tyriar committed Jul 13, 2021
    6ba98b1

  • add windows-build-tools workaround

    @TylerLeonhardt TylerLeonhardt committed Jul 9, 2021
    5868376

  • Updated How to Contribute (markdown)

    @jrieken jrieken committed Jun 25, 2021
    95aa2b1

  • Fix darwin -min targets

    @Tyriar Tyriar committed Jun 2, 2021
    4c7f376

  • Updated How to Contribute (markdown)

    @dbaeumer dbaeumer committed Apr 28, 2021
    a992f10