diff options
| author | Joe Carstairs <65492573+joeacarstairs@users.noreply.github.com> | 2024-02-01 22:30:29 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-02-01 22:30:29 +0000 |
| commit | d1d7e9c5bdc169149ccf0f5605b73a3921c111c8 (patch) | |
| tree | dc74a32ed9d46fad175b41c6acf79d54b3a81678 /README.md | |
| parent | 08a61f7bcbbb140863b0f2c3523929bfe4076d9f (diff) | |
Updates from staging (#79)
* Adds no-breadcrumbs variant of the navbar (#75)
* README: replaces 'Sycamost' with 'joeacarstairs' (#74)
* Design system board (#77)
* Simplifies theme selector syntax
* Adds .dark theming class
* Adds design system page (dev env only)
* Closes the Sangschaw (#78)
* Closes the Sangschaw
* Fixes syntax
---------
Co-authored-by: Joe Carstairs <65492573+Sycamost@users.noreply.github.com>
---------
Co-authored-by: Joe Carstairs <118172583+jcarstairs-scottlogic@users.noreply.github.com>
Co-authored-by: Joe Carstairs <65492573+Sycamost@users.noreply.github.com>
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 16 |
1 files changed, 8 insertions, 8 deletions
@@ -5,7 +5,7 @@ This is the Scots Leid Associe website, implemented in [Astro](https://astro.bui ## Gettin yokit ```bash -git clone https://github.com/Sycamost/lallans-wabsteid-astro.git \ +git clone https://github.com/joeacarstairs/lallans-wabsteid-astro.git \ && cd lallans-wabsteid-astro \ && npm install \ && npm run dev @@ -35,14 +35,14 @@ git clone https://github.com/Sycamost/lallans-wabsteid-astro.git \ 2. Make a suitably named branch on your fork. 3. Make your desired changes (see sections below for common cases). 4. Commit and push them on your branch. -5. Make a Pull Request to merge your changes into `Sycamost/deployment-staging`. +5. Make a Pull Request to merge your changes into `joeacarstairs/deployment-staging`. 6. A code owner (probably the Scots Language Society Webmaster) will review your Pull Request, ask - for any necessary changes, and when satisfied, merge it into `Sycamost/deployment-staging`. (This will - update the [staging deployment](#cicd) on + for any necessary changes, and when satisfied, merge it into `joeacarstairs/deployment-staging`. + (This will update the [staging deployment](#cicd) on [staging.scotsleidassocie.org](https://staging.scotsleidassocie.org).) -7. Code owners will merge `Sycamost/deployment-staging` into `Sycamost/deployment-production` at their discretion. - (This will update the production deployment on - [scotsleidassocie.org](https://scotsleidassocie.org).) +7. Code owners will merge `joeacarstairs/deployment-staging` into + `joeacarstairs/deployment-production` at their discretion. (This will update the production + deployment on [scotsleidassocie.org](https://scotsleidassocie.org).) ### Coding style @@ -148,6 +148,6 @@ To update production, you'll want to first merge your changes into `deployment-s Pull Request and getting it approved and merged. Once you've done that, given it five minutes to deploy, and you've checked that everything looks good on [staging.scotsleidassocie.org](https://staging.scotsleidassocie.org), -[make a Pull Request to merge deployment-staging into deployment-production](https://github.com/Sycamost/lallans-wabsteid-astro/compare/deployment-production...deployment-staging). +[make a Pull Request to merge deployment-staging into deployment-production](https://github.com/joeacarstairs/lallans-wabsteid-astro/compare/deployment-production...deployment-staging). Once that Pull Request is approved by a code owner, merge it in and it should update production in under five minutes. |