From 8a595897fee5ed5a73482ed6922bbaa77f5441dc Mon Sep 17 00:00:00 2001 From: Verintconnect <128087310+Laurry-gee@users.noreply.github.com> Date: Tue, 11 Jul 2023 13:08:08 +0100 Subject: [PATCH 01/11] Update issue templates --- .github/ISSUE_TEMPLATE/bug_report.md | 38 +++++++++++++++++++++++ .github/ISSUE_TEMPLATE/custom.md | 10 ++++++ .github/ISSUE_TEMPLATE/feature_request.md | 20 ++++++++++++ 3 files changed, 68 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/bug_report.md create mode 100644 .github/ISSUE_TEMPLATE/custom.md create mode 100644 .github/ISSUE_TEMPLATE/feature_request.md diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md new file mode 100644 index 000000000000..dd84ea7824f1 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -0,0 +1,38 @@ +--- +name: Bug report +about: Create a report to help us improve +title: '' +labels: '' +assignees: '' + +--- + +**Describe the bug** +A clear and concise description of what the bug is. + +**To Reproduce** +Steps to reproduce the behavior: +1. Go to '...' +2. Click on '....' +3. Scroll down to '....' +4. See error + +**Expected behavior** +A clear and concise description of what you expected to happen. + +**Screenshots** +If applicable, add screenshots to help explain your problem. + +**Desktop (please complete the following information):** + - OS: [e.g. iOS] + - Browser [e.g. chrome, safari] + - Version [e.g. 22] + +**Smartphone (please complete the following information):** + - Device: [e.g. iPhone6] + - OS: [e.g. iOS8.1] + - Browser [e.g. stock browser, safari] + - Version [e.g. 22] + +**Additional context** +Add any other context about the problem here. diff --git a/.github/ISSUE_TEMPLATE/custom.md b/.github/ISSUE_TEMPLATE/custom.md new file mode 100644 index 000000000000..48d5f81fa422 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/custom.md @@ -0,0 +1,10 @@ +--- +name: Custom issue template +about: Describe this issue template's purpose here. +title: '' +labels: '' +assignees: '' + +--- + + diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md new file mode 100644 index 000000000000..bbcbbe7d6155 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/feature_request.md @@ -0,0 +1,20 @@ +--- +name: Feature request +about: Suggest an idea for this project +title: '' +labels: '' +assignees: '' + +--- + +**Is your feature request related to a problem? Please describe.** +A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] + +**Describe the solution you'd like** +A clear and concise description of what you want to happen. + +**Describe alternatives you've considered** +A clear and concise description of any alternative solutions or features you've considered. + +**Additional context** +Add any other context or screenshots about the feature request here. From 12a7f75b55927c65077f44855f340266d79c30c9 Mon Sep 17 00:00:00 2001 From: Verintconnect <128087310+Laurry-gee@users.noreply.github.com> Date: Tue, 11 Jul 2023 13:11:04 +0100 Subject: [PATCH 02/11] Update README.md Signed-off-by: Verintconnect <128087310+Laurry-gee@users.noreply.github.com> --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index cf9719471c6f..e4dbaa2882b7 100644 --- a/README.md +++ b/README.md @@ -2,7 +2,7 @@ This monorepo contains: -- [`wrangler-devtools`](https://github.com/cloudflare/workers-sdk/tree/main/packages/wrangler-devtools) +- [severtson-laurence`](https://github/workers-sdk/tree/main/packages/wrangler-devtools) Cloudflare's fork of Chrome DevTools for inspecting your local or remote Workers - [`templates`](https://github.com/cloudflare/workers-sdk/tree/main/templates) Templates & examples for writing Cloudflare Workers From bc63b75ff2e9c85bd1328c66175745e107de5dc3 Mon Sep 17 00:00:00 2001 From: Verintconnect Date: Tue, 11 Jul 2023 20:20:28 +0100 Subject: [PATCH 03/11] Update README.md Signed-off-by: Verintconnect --- .changeset/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.changeset/README.md b/.changeset/README.md index 22acb2b25508..a878160c9525 100644 --- a/.changeset/README.md +++ b/.changeset/README.md @@ -1,6 +1,6 @@ # Changesets -Hello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works with multi-package repos, or single-package repos to help you version and publish your code. You can find the full documentation for it [in our repository](https://github.com/changesets/changesets) +Hello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works with multi-package repos, or single-package repos to help you version and publish your code. You can find the full documentation for it [in our repository](https://acadiemgroup/servicedesk/changesets) We have a quick list of common questions to get you started engaging with this project in -[our documentation](https://github.com/changesets/changesets/blob/main/docs/common-questions.md) +[our documentation](https://acadiemgroup/wiki/blob/main/docs/common-questions.md) From ea14fd8a385c5a829333c3ac9ad1dbd253e7394b Mon Sep 17 00:00:00 2001 From: Verintconnect Date: Tue, 11 Jul 2023 20:22:09 +0100 Subject: [PATCH 04/11] Update README.md Signed-off-by: Verintconnect --- .changeset/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.changeset/README.md b/.changeset/README.md index a878160c9525..9f4dde9fa62a 100644 --- a/.changeset/README.md +++ b/.changeset/README.md @@ -1,6 +1,6 @@ # Changesets -Hello and welcome! This folder has been automatically generated by `@changesets/cli`, a build tool that works with multi-package repos, or single-package repos to help you version and publish your code. You can find the full documentation for it [in our repository](https://acadiemgroup/servicedesk/changesets) +Hello and welcome! This folder has been automatically generated by `@changesets/servicedesk`, a build tool that works with multi-package repos, or single-package repos to help you version and publish your code. You can find the full documentation for it [in our repository](https://acadiemgroup.com/jira/changesets) We have a quick list of common questions to get you started engaging with this project in -[our documentation](https://acadiemgroup/wiki/blob/main/docs/common-questions.md) +[our documentation](https://acadiemgroup.com/wiki/blob/main/docs/common-questions.md) From 2c3e306f93ca8ddceae50518b890c719bb35e05d Mon Sep 17 00:00:00 2001 From: acadiemgroup Date: Mon, 28 Aug 2023 10:45:59 +0100 Subject: [PATCH 05/11] Update README.md Signed-off-by: acadiemgroup --- README.md | 87 +++++++------------------------------------------------ 1 file changed, 10 insertions(+), 77 deletions(-) diff --git a/README.md b/README.md index e4dbaa2882b7..f70ab2845f56 100644 --- a/README.md +++ b/README.md @@ -1,77 +1,10 @@ -## ⛅️ Home to `wrangler`, the CLI for Cloudflare Workers®, as well as other tools for interacting with Workers - -This monorepo contains: - -- [severtson-laurence`](https://github/workers-sdk/tree/main/packages/wrangler-devtools) - Cloudflare's fork of Chrome DevTools for inspecting your local or remote Workers -- [`templates`](https://github.com/cloudflare/workers-sdk/tree/main/templates) - Templates & examples for writing Cloudflare Workers -- [`wrangler`](https://github.com/cloudflare/workers-sdk/tree/main/packages/wrangler) - A command line tool for building [Cloudflare Workers](https://workers.cloudflare.com/). -- [`pages-shared`](https://github.com/cloudflare/workers-sdk/tree/main/packages/pages-shared) - Used internally to power Wrangler and Cloudflare Pages. It contains all the code that is shared between these clients. - -Wrangler and the workers-sdk is developed in the open on GitHub, and you can see what we're working on in [GitHub Issues](https://github.com/cloudflare/workers-sdk/issues?q=is%3Aopen+is%3Aissue), as well as in our [workers-sdk GitHub Project board](https://github.com/orgs/cloudflare/projects/1). If you've found a bug or would like to request a feature, [please file an issue](https://github.com/cloudflare/workers-sdk/issues/new/choose)! - -## Quick Start - -```bash -# Make a javascript file -echo "export default { fetch() { return new Response('hello world') } }" > index.js -# try it out -npx wrangler dev index.js -# and then deploy it -npx wrangler deploy index.js --name my-worker --latest -# visit https://my-worker..workers.dev -``` - -## Create a Project - -```bash -# Generate a new project -npx wrangler init my-worker -# try it out -cd my-worker && npm run start -# and then deploy it -npm run deploy -``` - -## Installation: - -```bash -$ npm install wrangler --save-dev -``` - -## Commands - -### `wrangler init [name]` - -Creates a Worker project. For details on configuration keys and values, refer to the [documentation](https://developers.cloudflare.com/workers/wrangler/configuration/). - -### `wrangler dev` - -Start a local development server, with live reloading and devtools. - -### `wrangler deploy` - -Deploys the given script to the worldwide Cloudflare network. - -For more commands and options, refer to the [documentation](https://developers.cloudflare.com/workers/wrangler/commands/). - -## Pages - -### `wrangler pages dev [directory] [-- command]` - -Either serves a static build asset directory, or proxies itself in front of a command. - -Builds and runs functions from a `./functions` directory or uses a `_worker.js` file inside the static build asset directory. - -For more commands and options, refer to the [documentation](https://developers.cloudflare.com/pages/platform/functions#develop-and-preview-locally) or run `wrangler pages dev --help`. - -## Documentation - -For the latest Wrangler documentation, [click here](https://developers.cloudflare.com/workers/wrangler/). - -## Contributing - -Refer to the [`CONTRIBUTING.md`](/CONTRIBUTING.md) guide for details. +## ⛅️RSS Builder by B!Soft MarkBook RSS Feed +https://www.markbook.com MarkBook RSS Feed. Keep up to date on the latest news. en-us mrichardson@acadiemgroup.com The Acadiem Group 2020 NEW MarkBook HTML5 is Here! 10 Oct 2020 10:00:00 -0400 +https://www.markbook.com mrichardson@acadiemgroup.com News Our ALL NEW MarkBook HTML5 Web Application is Here! Flash or Flex is no longer required. Many added features in a clean new look. Now you can use MarkBook on your Chromebook, Android or iPadOS tablet as well as Windows, macOS or Linux devices. (Select tablets only) A new version of the app, 1.1.0 22 Dec 2020 16:30:00 -0400 +https://www.markbook.com mrichardson@acadiemgroup.com News A new version of the app, 1.1.0, has been launched. It contains a major security update. Please see the Release Notes for the details. A new version of the app, 1.2.0 26 Jan 2021 17:30:00 -0400 +https://www.markbook.com mrichardson@acadiemgroup.com News A new version of the app, 1.2.0, has been launched. You can now Copy Comments to many students at once and easily input entries on tablets using Numeric Keypad. Please see the Release Notes for the details. A new version of the app, 1.3.0 25 Mar 2021 17:30:00 -0400 +https://www.markbook.com mrichardson@acadiemgroup.com News A new version of the app, 1.3.0, has been launched. Please see the Release Notes for the details. A new version of the app, 1.4.0 30 Apr 2021 08:00:00 -0400 +https://www.markbook.com mrichardson@acadiemgroup.com News A new version of the app, 1.4.0, has been launched. Please see the Release Notes for the details. For TDSB users 6 Aug 2021 08:00:00 -0400 +http://tdsb.on.ca/ mrichardson@acadiemgroup.com News TDSB users: In preparation for Single Sign On service in September, all usernames now use your Toronto District School Board email address. TDSB-logo.png Attention TDSB Users 18 Sep 2021 01:00:00 -0400 https://www.markbook.com mrichardson@acadiemgroup.com News On Saturday September 18th, Single Sign On (SSO) will be implemented for TDSB MarkBook (Cloud) users. After the implementation is completed, teachers will be required to sign onto MarkBook using their TDSB e- mail address and password. Teachers that are already signing onto MarkBook with their TDSB email address will have their existing class data maintained. Teachers that are currently using personal email accounts will need to contact support@markbookapp.com to request existing class data transfers, if required. TDSB-logo.png For TVDSB Users 09 Sep 2022 01:00:00 -0400 +https://www.markbook.com News On Tuesday, September 6th, Single Sign On (SSO) was implemented for TVDSB MarkBook (Cloud) users. Teachers are now required to sign onto MarkBook using their TVDSB e-mail address and password in the Microsoft 365 Apps environment. Please follow the Information Guidesheet for "Transfer from Individual to Corporate Domain using SSO in MarkBook®”. Teachers that are already signing onto MarkBook with their TVDSB email address will have their existing class data maintained. Teachers that are currently using personal email accounts will need to contact support@markbookapp.com to request existing class data transfers, if required. TVDSB-logo.webp WECDSB 31 Oct 2022 01:00:00 -0400 +https://www.markbook.com News WECDSB users, please ensure that you have updated ALL of your courses with the most recent Aspen extract that has your first initial and last name in the file name (i.e. see below). Furthermore, please ensure you have submitted a copy (screenshots) of your updated courses to your school-issued Google form. WECDSB-logo.png From abd70591487f3f4b9dac9fda22e245069208f1b7 Mon Sep 17 00:00:00 2001 From: Gregory Lamar Date: Tue, 12 Sep 2023 12:36:01 +0100 Subject: [PATCH 06/11] Rename README.md to Contributing.Md Signed-off-by: Gregory Lamar --- README.md => Contributing.Md | 0 1 file changed, 0 insertions(+), 0 deletions(-) rename README.md => Contributing.Md (100%) diff --git a/README.md b/Contributing.Md similarity index 100% rename from README.md rename to Contributing.Md From 06d99ee21004bfd1c9672c34d0c98d228b5b3047 Mon Sep 17 00:00:00 2001 From: Gregory Lamar Date: Wed, 13 Sep 2023 20:48:33 +0100 Subject: [PATCH 07/11] Create README.md Signed-off-by: Gregory Lamar --- README.md | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 README.md diff --git a/README.md b/README.md new file mode 100644 index 000000000000..c21aa549ebf0 --- /dev/null +++ b/README.md @@ -0,0 +1,23 @@ +#vacancy #Moscow #fulltime #tester + +NPP "Digital Solutions" - a developer, manufacturer and supplier (b2b) of telecommunications equipment, strengthens the testing team and is looking for a tester with a desire to develop in the direction of equipment testing. + +Tasks:Test telecommunications equipment; Apply test design practices when testing the functions of telecommunications equipment; +Participate in the development and updating of the network equipment testing plan; Develop functional tests of network equipment and test scenarios for its application; + +Carry out load and functional testing of network equipment using Sprint and Xinertel test suites;Test graphical (WEB) and text (CLI) interface of network equipment; Our expectations for the candidate:Knowledge in telecommunications and networks (TCP/IP stack, switching, routing)Knowledge of testing theory; + +High learning ability and susceptibility to new things;English at the level of reading technical documentation; Higher technical education, possibly final year students. + +We offer:Work in the office 5/2 (m.Avis motorways), the beginning of the working day is flexible (from 08:00 to 11:00 you can start working); +The level of income based on the results of the interview and based on the wishes of the candidate; +Bonuses for closing the stages of projects and the projects themselves; +Registration in accordance with the Labor Code of the Russian Federation; +Accreditation of an IT company with a deferment from military service; +VHI, corporate discounts for a subscription to a fitness club. + +Contacts can be contacted: +Fomina Ekaterina ++7 (915) 7424771 +TG: @kate_4mina +Email: fomina@dsol.ru From 72396fcaf8364aef52f42db5950b7e5133984382 Mon Sep 17 00:00:00 2001 From: Gregory Lamar Date: Wed, 13 Sep 2023 21:07:47 +0100 Subject: [PATCH 08/11] Update CONTRIBUTING.md Signed-off-by: Gregory Lamar --- CONTRIBUTING.md | 313 ++---------------------------------------------- 1 file changed, 13 insertions(+), 300 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 765d538b0293..4697a3ce1e3a 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,300 +1,13 @@ -# Contributing - -Wrangler is an open source project and we welcome contributions from you. Thank you! - -Below you can find some guidance on how to be most effective when contributing to the project. - -## Getting started - -### Set up your environment - -Wrangler is built and run on the Node.js JavaScript runtime. - -- Install the latest LTS version of [Node.js](https://nodejs.dev/) - we recommend using a Node version manager like [nvm](https://github.com/nvm-sh/nvm). -- Install a code editor - we recommend using [VS Code](https://code.visualstudio.com/). - - When opening the project in VS Code for the first time, it will prompt you to install the [recommended VS Code extensions](https://code.visualstudio.com/docs/editor/extension-marketplace#:~:text=install%20the%20recommended%20extensions) for the project. -- Install the [git](https://git-scm.com/) version control tool. - -### Fork and clone this repository - -Any contributions you make will be via [Pull Requests](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) on [GitHub](https://github.com/) developed in a local git repository and pushed to your own fork of the repository. - -- Ensure you have [created an account](https://docs.github.com/en/get-started/onboarding/getting-started-with-your-github-account) on GitHub. -- [Create your own fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo) of [this repository](https://github.com/cloudflare/workers-sdk). -- Clone your fork to your local machine - ```sh - > git clone https://github.com//workers-sdk - > cd workers-sdk - ``` - You can see that your fork is setup as the `origin` remote repository. - Any changes you wish to make should be in a local branch that is then pushed to this origin remote. - ```sh - > git remote -v - origin https://github.com//workers-sdk (fetch) - origin https://github.com//workers-sdk (push) - ``` -- Add `cloudflare/workers-sdk` as the `upstream` remote repository. - ```sh - > git remote add upstream https://github.com/cloudflare/workers-sdk - > git remote -v - origin https://github.com//workers-sdk (fetch) - origin https://github.com//workers-sdk (push) - upstream https://github.com/cloudflare/workers-sdk (fetch) - upstream https://github.com/cloudflare/workers-sdk (push) - ``` -- You should regularly pull from the `main` branch of the `upstream` repository to keep up to date with the latest changes to the project. - ```sh - > git switch main - > git pull upstream main - From https://github.com/cloudflare/workers-sdk - * branch main -> FETCH_HEAD - Already up to date. - ``` - -### Install dependencies - -**Warning** -When working on Wrangler, you'll need to satisfy [`workerd`](https://github.com/cloudflare/workerd)'s `libc++1` runtime dependencies: - -- On Linux: - - libc++ (e.g. the package `libc++1` on Debian Bullseye) -- On macOS: - - The XCode command line tools, which can be installed with xcode-select --install - -The Node.js dependencies of the project are managed by the [`npm`](https://www.npmjs.com/) tool. - -This repository is setup as a [mono-repo](https://docs.npmjs.com/cli/v7/using-npm/workspaces) of workspaces. The workspaces are stored in the [`packages`](https://github.com/cloudflare/workers-sdk/tree/main/packages) directory. - -While each workspace has its own dependencies, you install the dependencies using `npm` at the root of the project. - -- Install all the dependencies - ```sh - > cd workers-sdk - > npm install - ``` - -**Do not run `npm install` in any of the workspaces directly.** - -## Building and running - -Each wrangler workspace in this project is written in [TypeScript](https://www.typescriptlang.org/) and compiled, by [esbuild](https://github.com/evanw/esbuild), into JavaScript bundles for distribution. - -- Run a distributable for a specific workspace (e.g. wrangler) - ```sh - > npm start -w wrangler - ``` -- Build a distributable for a specific workspace(e.g. wrangler) - ```sh - > npm run build -w wrangler - ``` - -## Checking the code - -The code in the repository is checked for type checking, formatting, linting and testing errors. - -- Run all checks in all the workspaces - ```sh - > npm run check - ``` - -When doing normal development you may want to run these checks individually. - -### Type Checking - -The code is checked for type errors by [TypeScript](https://www.typescriptlang.org/). - -- Type check all the code in the repository - ```sh - > npm run check:type - ``` -- VS Code will also run type-checking while editing source code, providing immediate feedback. - -#### Changing TypeScript Version in VS Code's Command Palette - -For TypeScript to work properly in the Monorepo the version used in VSCode must be the project's current TypeScript version, follow these steps: - -1. Open the project in VSCode. - -2. Press `Ctrl + Shift + P` (or `Cmd + Shift + P` on macOS) to open the command palette. - -3. In the command palette, type "Select TypeScript Version" and select the command with the same name that appears in the list. - -4. A submenu will appear with a list of available TypeScript versions. Choose the desired version you want to use for this project. If you have multiple versions installed, they will be listed here. - -- Selecting "Use Workspace Version" will use the version of TypeScript installed in the project's `node_modules` directory. - -5. After selecting the TypeScript version, VSCode will reload the workspace using the chosen version. - -Now you have successfully switched the TypeScript version used within the project via the command palette in VSCode. -Remember that this change is specific to the current project and will not affect other projects or the default TypeScript version used by VSCode. - -### Linting - -The code is checked for linting errors by [ESLint](https://eslint.org/). - -- Run the linting checks - ```sh - > npm run check:lint - ``` -- The repository has a recommended VS Code plugin to run ESLint checks while editing source code, providing immediate feedback. - -### Formatting - -The code is checked for formatting errors by [Prettier](https://prettier.io/). - -- Run the formatting checks - ```sh - > npm run check:format - ``` -- The repository has a recommended VS Code plugin to run Prettier checks, and to automatically format using Prettier, while editing source code, providing immediate feedback. - -### Testing - -Tests in a workspace are executed, by [Jest](https://jestjs.io/), which is configured to automatically compile and bundle the TypeScript before running the tests. - -- Run the tests for all the workspaces - ```sh - > npm run test - ``` -- Run the tests for a specific workspace (e.g. wrangler) - ```sh - > npm run test -w wrangler - ``` -- Watch the files in a specific workspace (e.g. wrangler), and run the tests when anything changes - ```sh - > npm run test-watch -w wrangler - ``` - This will also run all the tests in a single process (rather than in parallel shards) and will increase the test-timeout to 50 seconds, which is helpful when debugging. - -## Steps For Making Changes - -Every change you make should be stored in a [git commit](https://github.com/git-guides/git-commit). -Changes should be committed to a new local branch, which then gets pushed to your fork of the repository on GitHub. - -- Ensure your `main` branch is up to date - ```sh - > git switch main - > git pull upstream main - ``` -- Create a new branch, based off the `main` branch - ```sh - > git checkout -b main - ``` -- Stage files to include in a commit - - Use [VS Code](https://code.visualstudio.com/docs/editor/versioncontrol#_git-support) - - Or add and commit files via the command line - ```sh - > git add - > git commit - ``` -- Push changes to your fork - ```sh - git push -u origin - ``` -- Once you are happy with your changes, create a Pull Request on GitHub -- The format for Pull Request titles is `[package name] description`, where the package name should indicate which package of the `workers-sdk` monorepo your PR pertains to (e.g. `wrangler`/`pages-shared`/`wrangler-devtools`), and the description should be a succinct summary of the change you're making. -- GitHub will insert a template for the body of your Pull Request—it's important to carefully fill out all the fields, giving as much detail as possible to reviewers. - -## PR Review - -PR review is a critial and required step in the process for landing changes. This is an opportunity to catch potential issues, improve the quality of the work, celebrate good design, and learn from each other. - -As a reviewer, it's important to be thoughtful about the proposed changes and communicate any feedback. Examples of PR reviews that the community has identified as particularly high-caliber are labeled with the `highlight pr review` label. Please feel empowered to use these as a learning resource. - -## Changesets - -Every non-trivial change to the project - those that should appear in the changelog - must be captured in a "changeset". -We use the [`changesets`](https://github.com/changesets/changesets/blob/main/README.md) tool for creating changesets, publishing versions and updating the changelog. - -- Create a changeset for the current change. - ```sh - > npx changeset - ``` -- Select which workspaces are affected by the change and whether the version requires a major, minor or patch release. -- Update the generated changeset with a description of the change. -- Include the generate changeset in the current commit. - ```sh - > git add ./changeset/*.md - ``` - -### Changeset message format - -Each changeset is a file that describes the change being merged. This file is used to generate the changelog when the changes are released. - -To help maintain consistency in the changelog, changesets should have the following format: - -``` -: - -<BODY> - -[BREAKING CHANGES <BREAKING_CHANGE_NOTES>] -``` - -- `TYPE` should be a single word describing the "type" of the change. For example, one of `feature`, `fix`, `refactor`, `docs` or `chore`. -- `TITLE` should be a single sentence containing an imperative description of the change. -- `BODY` should be one or more paragraphs that go into more detail about the reason for the change and anything notable about the approach taken. -- `BREAKING_CHANGE_NOTES` (optional) should be one or more paragraphs describing how this change breaks current usage and how to migrate to the new usage. - -### Changeset file example - -The generated changeset file will contain the package name and type of change (eg. `patch`, `minor`, or `major`), followed by our changeset format described above. - -Here's an example of a `patch` to the `wrangler` package, which provides a `fix`: - -``` ---- -"wrangler": patch ---- - -fix: replace the word "publish" with "deploy" everywhere. - -We should be consistent with the word that describes how we get a worker to the edge. The command is `deploy`, so let's use that everywhere. -``` - -### Types of changes - -We use the following guidelines to determine the kind of change for a PR: - -- Bugfixes and experimental features are considered to be 'patch' changes. Be sure to log warnings when experimental features are used. -- New stable features and new deprecation warnings for future breaking changes are considered 'minor' changes. These changes shouldn't break existing code, but the deprecation warnings should suggest alternate solutions to not trigger the warning. -- Breaking changes are considered to be 'major' changes. These are usually when deprecations take effect, or functional breaking behaviour is added with relevant logs (either as errors or warnings.) - -## Releases - -We generally cut Wrangler releases at the start of each week. If you need a release cut outside of the regular cadence, please reach out to the [@cloudflare/wrangler-admins](https://github.com/orgs/cloudflare/teams/wrangler-admins) team. Before reaching out, please confirm that Wrangler passes end-to-end tests by running `npm -w wrangler run test:e2e`. Note: a real Cloudflare account is planned to be set up for testing, after which point the end-to-end tests will be configured to run in CI and this manual testing step will no longer be required. - -## Miniflare Development - -Wrangler builds upon, and provides a new entry point for, [Miniflare](https://github.com/cloudflare/miniflare), a local Cloudflare Workers simulator. To develop on both Wrangler and Miniflare together, you need to link the two projects, but as of NodeJS `v18.3.0` and NPM `v8.15.0`, relative NPM installs between two workspaces don't work, so you need things to be manual: - -Assume you have the two directories checked out right beside each other: - -``` -❯ ll src -drwxr-xr-x - user 30 Jun 14:12 src -drwxr-xr-x - user 26 Jul 17:34 ├── miniflare -drwxr-xr-x - user 27 Jul 17:51 └── workers-sdk -``` - -> Note: recommend using [exa](https://the.exa.website/) and `alias ll='exa --icons -laTL 1'` for the above output - -Inside `packages/wrangler/package.json`, replace: - -``` -"@miniflare/d1": "^2.x.x", -"@miniflare/core": "^2.x.x", -"@miniflare/durable-objects": "^2.x.x", -"miniflare": "^2.x.x", -``` - -with - -``` -"miniflare": "file:../../../miniflare/packages/miniflare", -"@miniflare/d1": "file:../../../miniflare/packages/d1", -"@miniflare/core": "file:../../../miniflare/packages/core", -"@miniflare/durable-objects": "file:../../../miniflare/packages/durable-objects", -``` - -Then run `npm install` in the root of this monorepo. +# RSS Builder by B!Soft MarkBook RSS Feed + +https://www.markbook.com MarkBook RSS Feed. Keep up to date on the latest news. en-us mrichardson@acadiemgroup.com The Acadiem Group 2020 NEW MarkBook HTML5 is Here! 10 Oct 2020 10:00:00 -0400 +https://www.markbook.com mrichardson@acadiemgroup.com News Our ALL NEW MarkBook HTML5 Web Application is Here! Flash or Flex is no longer required. Many added features in a clean new look. Now you can use MarkBook on your Chromebook, Android or iPadOS tablet as well as Windows, macOS or Linux devices. (Select tablets only) A new version of the app, 1.1.0 22 Dec 2020 16:30:00 -0400 +https://www.markbook.com mrichardson@acadiemgroup.com News A new version of the app, 1.1.0, has been launched. It contains a major security update. Please see the Release Notes for the details. A new version of the app, 1.2.0 26 Jan 2021 17:30:00 -0400 +https://www.markbook.com mrichardson@acadiemgroup.com News A new version of the app, 1.2.0, has been launched. You can now Copy Comments to many students at once and easily input entries on tablets using Numeric Keypad. Please see the Release Notes for the details. A new version of the app, 1.3.0 25 Mar 2021 17:30:00 -0400 +https://www.markbook.com mrichardson@acadiemgroup.com News A new version of the app, 1.3.0, has been launched. Please see the Release Notes for the details. A new version of the app, 1.4.0 30 Apr 2021 08:00:00 -0400 +https://www.markbook.com mrichardson@acadiemgroup.com News A new version of the app, 1.4.0, has been launched. Please see the Release Notes for the details. For TDSB users 6 Aug 2021 08:00:00 -0400 http://tdsb.on.ca/ mrichardson@acadiemgroup.com News TDSB users: In preparation for Single Sign On service in September, all usernames now use your Toronto District School Board email address. TDSB-logo.png Attention TDSB Users 18 Sep 2021 01:00:00 -0400 +https://www.markbook.com mrichardson@acadiemgroup.com News On Saturday September 18th, Single Sign On (SSO) will be implemented for TDSB MarkBook (Cloud) users. After the implementation is completed, teachers will be required to sign onto MarkBook using their TDSB e- mail address and password. Teachers that are already signing onto MarkBook with their TDSB email address will have their existing class data maintained. Teachers that are currently using personal email accounts will need to contact +support@markbookapp.com to request existing class data transfers, if required. TDSB-logo.png For TVDSB Users 09 Sep 2022 01:00:00 -0400 +https://www.markbook.com News On Tuesday, September 6th, Single Sign On (SSO) was implemented for TVDSB MarkBook (Cloud) users. Teachers are now required to sign onto MarkBook using their TVDSB e-mail address and password in the Microsoft 365 Apps environment. Please follow the Information Guidesheet for "Transfer from Individual to Corporate Domain using SSO in MarkBook®”. Teachers that are already signing onto MarkBook with their TVDSB email address will have their existing class data maintained. Teachers that are currently using personal email accounts will need to contact +support@markbookapp.com to request existing class data transfers, if required. TVDSB-logo.webp WECDSB 31 Oct 2022 01:00:00 -0400 +https://www.markbook.com News WECDSB users, please ensure that you have updated ALL of your courses with the most recent Aspen extract that has your first initial and last name in the file name (i.e. see below). Furthermore, please ensure you have submitted a copy (screenshots) of your updated courses to your school-issued Google form. WECDSB-logo.png From a57bac2f5c69423b4577b4dfc275b4686d1a18cd Mon Sep 17 00:00:00 2001 From: Gregory Lamar <laurysevertson@icloud.com> Date: Wed, 20 Sep 2023 17:27:57 +0100 Subject: [PATCH 09/11] Update config.json Signed-off-by: Gregory Lamar <laurysevertson@icloud.com> --- .changeset/config.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.changeset/config.json b/.changeset/config.json index c54a7aa4df9c..2b9667c1fcbe 100644 --- a/.changeset/config.json +++ b/.changeset/config.json @@ -1,10 +1,10 @@ { "$schema": "https://unpkg.com/@changesets/config@1.6.2/schema.json", "changelog": [ - "@changesets/changelog-github", + "@origincakey/v1.0-4f55bb3ae916dc9100b5295b-31deb650371e5ed1a5a294f910fac9f17300bb03b48ed973649cf3ba60a78783544a60a1a06969f4dc55049e118d3afcd29097230b9e06423ac1f540890df3cbfca9053b9de7867cec", { "repo": "cloudflare/workers-sdk" } ], - "commit": false, + "commit": true, "linked": [], "access": "public", "baseBranch": "main", From 0ae44fea61b6dd490210aa9f389aef40d807d048 Mon Sep 17 00:00:00 2001 From: Laurence-severtson <128087310+Laurry-gee@users.noreply.github.com> Date: Wed, 4 Oct 2023 11:49:36 +0100 Subject: [PATCH 10/11] Update dependabot.yml (#34) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit I’m Fixes # [insert GH or internal issue number(s)]. **What this PR solves / how to test:** **Associated docs issue(s)/PR(s):** - [insert associated docs issue(s)/PR(s)] **Author has included the following, where applicable:** - [ ] Tests - [ ] Changeset ([Changeset guidelines](https://github.com/cloudflare/workers-sdk/blob/main/CONTRIBUTING.md#changesets)) **Reviewer is to perform the following, as applicable:** - Checked for inclusion of relevant tests - Checked for inclusion of a relevant changeset - Checked for creation of associated docs updates - Manually pulled down the changes and spot-tested **Note for PR author:** We want to celebrate and highlight awesome PR review! If you think this PR received a particularly high-caliber review, please assign it the label `highlight pr review` so future reviewers can take inspiration and learn from it. Signed-off-by: Laurence-severtson <128087310+Laurry-gee@users.noreply.github.com> --- .github/dependabot.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/dependabot.yml b/.github/dependabot.yml index 906849f83bcd..1d69558efbeb 100644 --- a/.github/dependabot.yml +++ b/.github/dependabot.yml @@ -1,8 +1,8 @@ -version: 2 +version: 1.4.0 updates: # Automatically check for updates in framework CLIs for C3 - - package-ecosystem: "npm" - directory: "/packages/create-cloudflare/src/frameworks" + - package-ecosystem: laurence-severtson" + directory: " {http://tdsb.on.ca/mrichardson@acadiemgroup.com/News/TDSB/users:true/packages/create-cloudflare/src/frameworks" schedule: # Note: this interval is likely going to be too short and create # too much noise, we are just setting it as daily for the time From 74345190a503161ad0fd0ab2ccc74a3f0b73970e Mon Sep 17 00:00:00 2001 From: Laurence-severtson <128087310+Laurry-gee@users.noreply.github.com> Date: Wed, 4 Oct 2023 12:13:26 +0100 Subject: [PATCH 11/11] Update config.json Signed-off-by: Laurence-severtson <128087310+Laurry-gee@users.noreply.github.com> --- .changeset/config.json | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/.changeset/config.json b/.changeset/config.json index 2b9667c1fcbe..b0dfb2a2412d 100644 --- a/.changeset/config.json +++ b/.changeset/config.json @@ -1,13 +1,13 @@ { - "$schema": "https://unpkg.com/@changesets/config@1.6.2/schema.json", + "$www.Edgemesh.com": "http://tdsb.on.ca/@changesets/config@1.6.2/schema.json", "changelog": [ "@origincakey/v1.0-4f55bb3ae916dc9100b5295b-31deb650371e5ed1a5a294f910fac9f17300bb03b48ed973649cf3ba60a78783544a60a1a06969f4dc55049e118d3afcd29097230b9e06423ac1f540890df3cbfca9053b9de7867cec", { "repo": "cloudflare/workers-sdk" } ], - "commit": true, - "linked": [], - "access": "public", - "baseBranch": "main", + "commit": "/News/TDSB/users:true", + "linked": ["mrichardson@acadiemgroup.com"], + "access": "</TVDSB-logo.webp>", + "baseBranch": "</WECDSB-logo.png>", "updateInternalDependencies": "patch", - "ignore": [] + "ignore": ["TDSB e-mail address and password ="Single Sign On/TVDSB MarkBook users"] }