Meta tags:
description= CLI tool for Angular. Contribute to angular/angular-cli development by creating an account on GitHub.;
Headings (most frequently used words):
contributing, navigation, commit, footer, md, file, breadcrumbs, an, issue, guidelines, message, submitting, pull, request, to, angular, devkit, menu, repository, filesexpand, tree, latest, history, metadata, and, controls, code, of, conduct, got, question, or, problem, found, want, feature, submission, coding, rules, signing, the, cla, spam, policy, pr, format, revert, type, scope, subject, examples, body, after, your, is, merged,
Text of the page (most frequently used words):
the (89), and (47), #angular (36), you (27), commit (23), your (23), github (22), for (22), that (20), code (16), change (16), cli (14), fix (14), can (13), this (13), our (13), changes (13), issue (13), are (13), devkit (13), git (13), with (12), line (12), main (12), branch (12), pull (11), blank (10), all (10), message (9), should (8), breaking (8), issues (8), scope (8), feature (8), from (8), build (8), repository (8), request (8), not (7), please (7), new (7), messages (7), more (7), file (7), footer (6), sign (6), have (6), before (6), any (6), must (6), description (6), will (6), type (6), bug (6), follow (6), guidelines (6), coding (6), problem (6), help (6), support (6), security (5), cla (5), requests (5), also (5), fixes (5), use (5), body (5), subject (5), test (5), without (5), documentation (5), header (5), rules (5), features (5), out (5), questions (5), better (5), question (5), stackoverflow (5), actions (5), time (4), information (4), one (4), deprecated (4), what (4), path (4), add (4), schematics (4), don (4), changelog (4), project (4), local (4), but (4), history (4), tests (4), upstream (4), delete (4), push (4), open (4), want (4), submit (4), submitting (4), minimal (4), like (4), would (4), contributing (4), raw (4), copilot (4), status (3), navigation (3), see (3), spam (3), policy (3), need (3), through (3), contributor (3), signed (3), deprecation (3), section (3), followed (3), update (3), includes (3), about (3), place (3), cannot (3), examples (3), refactor (3), first (3), following (3), general (3), tooling (3), release (3), api (3), ensure (3), source (3), keep (3), these (3), latest (3), version (3), merge (3), business (3), make (3), search (3), submission (3), bugs (3), reproduce (3), scenario (3), might (3), confirm (3), work (3), conduct (3), copy (3), blame (3), quality (3), another (3), tab (3), window (3), refresh (3), session (3), reload (3), developers (3), customer (3), enterprise (3), grade (3), action (2), docs (2), community (2), details (2), form (2), license (2), agreement (2), sending (2), accepted (2), signing (2), start (2), detailed (2), recommended (2), summary (2), migration (2), instructions (2), number (2), prs (2), close (2), imperative (2), present (2), tense (2), changed (2), nor (2), previous (2), command (2), json (2), prevent (2), webpack (2), create (2), generated (2), next (2), improvements (2), suite (2), point (2), functionality (2), style (2), configuration (2), system (2), reverts (2), reverted (2), where (2), hash (2), revert (2), 100 (2), characters (2), allows (2), read (2), well (2), optional (2), has (2), format (2), public (2), checkout (2), origin (2), follows (2), after (2), merged (2), current (2), target (2), label (2), else (2), rebase (2), run (2), automatically (2), files (2), using (2), conventions (2), soon (2), developer (2), consider (2), able (2), back (2), going (2), save (2), find (2), fixing (2), used (2), available (2), outline (2), proposal (2), even (2), people (2), answers (2), much (2), got (2), 305 (2), lines (2), 225 (2), loc (2), breadcrumbs (2), insights (2), 196 (2), universe (2), training (2), integrations (2), stories (2), center (2), learn (2), products (2), secret (2), perform, share, personal, manage, cookies, contact, privacy, terms, 2026, inc, corporations, print, scan, email, fax, mail, individuals, simple, click, quick, process, promise, similarly, short, mentions, phrase, closes, contain, deprecations, reference, jira, tickets, other, related, example, just, include, motivation, contrast, behavior, publishing, workflow, xyz, invalid, move, classes, together, flubber, grassing, valid, dot, end, concise, direct, capitalize, letter, contains, succinct, ngtools, core, architect, ssr, pwa, list, supported, scopes, name, npm, package, affected, perceived, person, reading, only, applies, scripts, corrections, made, improves, performance, perf, previously, discovered, failure, creates, feat, which, exclusively, affects, specific, begin, say, sha, being, longer, easier, various, tools, mandatory, each, consists, special, very, precise, over, how, formatted, leads, easy, when, looking, generate, log, readable, wrap, google, javascript, guide, methods, tbc, documented, specs, unit, e2e, tested, consistency, throughout, mind, working, check, remote, either, web, shell, safely, thank, contribution, caretaker, within, days, correct, author, collaborator, last, reviewer, pre, emptively, address, conflicts, once, approved, done, suites, still, passing, required, updates, suggest, then, send, note, option, edited, descriptive, adherence, necessary, because, notes, full, described, pass, coming, patch, including, appropriate, cases, accept, closed, relates, duplicate, effort, selecting, filling, template, templates, unfortunately, investigate, reproduction, hear, enough, info, reproduced, insisting, order, maintainers, ultimately, interestingly, experience, users, often, problems, themselves, while, preparing, understand, sometimes, hard, extract, essentials, bits, larger, base, really, isolate, quickly, right, most, importantly, case, fails, 3rd, party, libraries, their, versions, possible, having, reproducible, gives, wealth, important, forth, additional, tracker, maybe, already, exists, discussion, inform, workarounds, readily, crafted, directly, submitted, small, discussed, allow, coordinate, efforts, duplication, craft, successfully, into, major, sure, kind, implement, mistake, found, chat, real, reach, via, gitter, channel, systematically, closing, redirecting, voting, assures, best, prominently, visible, stay, viewing, answer, someone, there, thousands, willing, ask, since, reports, chances, getting, answered, tagged, tag, inclusive, love, contribute, than, today, here, edit, download, preview, metadata, controls, top, expand, tree, items, dismiss, alert, switched, accounts, appearance, settings, pricing, event, talks, workshops, partners, company, forum, events, webinars, blog, resource, connect, resources, premium, advanced, ons, trust, why, evaluate, industries, government, manufacturing, financial, services, healthcare, industry, nonprofits, startups, team, enterprises, stage, businesses, across, articles, sponsors, trending, repos, explore, customize, certifications, scanning, leak, prevention, protection, vulnerability, detection, remediation, secure, cloud, development, environments, codespaces, analysis, enforcement, automation, ship, agent, tasks, projects, automated, hosting, review, collaboration, platform, menu, skip, content,
Text of the page (random words):
angular cli contributing md at main angular angular cli github skip to content navigation menu sign in products platform github repository hosting code review and collaboration copilot ai coding agent for tasks projects and automated work build ship actions ci cd and automation code quality quality analysis fixes and enforcement codespaces cloud development environments secure code security vulnerability detection and remediation secret protection secret scanning and leak prevention all features developers learn documentation training certifications build build with copilot customize copilot integrations explore trending repos github sponsors developer articles changelog changelog your source for the latest features improvements and fixes across github products all in one place businesses by stage enterprises team startups nonprofits by industry healthcare financial services manufacturing government see all industries evaluate github why github customer stories business insights trust center add ons github advanced security enterprise grade code security copilot for business enterprise grade ai features premium support enterprise grade 24 7 support resources learn connect documentation resource center blog events webinars community forum customer stories integrations support customer support training github status company about partners changelog github universe github universe the event for developers by developers talks workshops and what s next for github pricing search sign in sign up appearance settings you signed in with another tab or window reload to refresh your session you signed out in another tab or window reload to refresh your session you switched accounts on another tab or window reload to refresh your session dismiss alert message angular angular cli repository navigation code issues 196 196 pull requests 19 19 actions security and quality 8 8 insights more items files expand file tree main breadcrumbs angular cli contributing md copy path blame more file actions blame more file actions latest commit history history history 305 lines 225 loc 12 5 kb main breadcrumbs angular cli contributing md copy path top file metadata and controls preview code blame 305 lines 225 loc 12 5 kb raw copy raw file download raw file outline edit and raw actions contributing to angular devkit we would love for you to contribute to devkit and help make it even better than it is today as a contributor here are the guidelines we would like you to follow code of conduct question or problem issues and bugs feature requests submission guidelines coding rules commit message guidelines signing the cla spam policy code of conduct help us keep angular open and inclusive please read and follow our code of conduct got a question or problem please do not open issues for the general support questions as we want to keep github issues for bug reports and feature requests you ve got much better chances of getting your question answered on stackoverflow where the questions should be tagged with tag angular cli or angular devkit stackoverflow is a much better place to ask questions since there are thousands of people willing to help on stackoverflow questions and answers stay available for public viewing so your question answer might help someone else stackoverflow s voting system assures that the best answers are prominently visible to save your and our time we will be systematically closing all the issues that are requests for general support and redirecting people to stackoverflow if you would like to chat about the question in real time you can reach out via our gitter channel found an issue if you find a bug in the source code or a mistake in the documentation you can help us by submitting an issue to our github repository even better you can submit a pull request with a fix want a feature you can request a new feature by submitting an issue to our github repository if you would like to implement a new feature please submit an issue with a proposal for your work first to be sure that we can use it please consider what kind of change it is for a major feature first open an issue and outline your proposal so that it can be discussed this will also allow us to better coordinate our efforts prevent duplication of work and help you to craft the change so that it is successfully accepted into the project small features can be crafted and directly submitted as a pull request submission guidelines submitting an issue before you submit an issue please search the issue tracker maybe an issue for your problem already exists and the discussion might inform you of workarounds readily available we want to fix all the issues as soon as possible but before fixing a bug we need to reproduce and confirm it having a reproducible scenario gives us wealth of important information without going back forth to you with additional questions like version of angular cli used angular json configuration version of angular devkit used 3rd party libraries and their versions and most importantly a use case that fails a minimal reproduce scenario using allows us to quickly confirm a bug or point out coding problem as well as confirm that we are fixing the right problem we will be insisting on a minimal reproduce scenario in order to save maintainers time and ultimately be able to fix more bugs interestingly from our experience users often find coding problems themselves while preparing a minimal repository we understand that sometimes it might be hard to extract essentials bits of code from a larger code base but we really need to isolate the problem before we can fix it unfortunately we are not able to investigate fix bugs without a minimal reproduction so if we don t hear back from you we are going to close an issue that don t have enough info to be reproduced you can file new issues by selecting from our new issue templates and filling out the issue template submitting a pull request pr before you submit your pull request pr consider the following guidelines search github for an open or closed pr that relates to your submission you don t want to duplicate effort please sign our contributor license agreement cla before sending prs we cannot accept code without this make your changes in a new git branch git checkout b my fix branch main create your patch including appropriate test cases follow our coding rules run the full angular cli and devkit test suite as described in the developer documentation and ensure that all tests pass coming soon commit your changes using a descriptive commit message that follows our commit message conventions adherence to these conventions is necessary because release notes are automatically generated from these messages git commit a note the optional commit a command line option will automatically add and rm edited files push your branch to github git push origin my fix branch in github send a pull request to angular angular cli main if we suggest changes then make the required updates re run the angular devkit test suites to ensure tests are still passing once your pr is approved and you are done with any follow up changes rebase to the current main to pre emptively address any merge conflicts git rebase upstream main i git push f add the action merge label and the correct target label if pr author has the project collaborator status or else the last reviewer should do this the current caretaker will merge the pr to the target branch es within 1 2 business days that s it thank you for your contribution after your pull request is merged after your pull request is merged you can safely delete your branch and pull the changes from the main upstream repository delete the remote branch on github either through the github web ui or your local shell as follows git push origin delete my fix branch check out the main branch git checkout main f delete the local branch git branch d my fix branch update your local main with the latest upstream version git pull ff upstream main coding rules to ensure consistency throughout the source code keep these rules in mind as you are working all features or bug fixes must be tested by one or more specs unit tests or e2e tests all public api methods must be documented details tbc we follow google s javascript style guide but wrap all code at 100 characters commit message guidelines we have very precise rules over how our git commit messages can be formatted this leads to more readable messages that are easy to follow when looking through the project history but also we use the git commit messages to generate the angular devkit change log commit message format each commit message consists of a header a body and a footer the header has a special format that includes a type a scope and a subject type scope subject blank line body blank line footer the header is mandatory and the scope of the header is optional any line of the commit message cannot be longer 100 characters this allows the message to be easier to read on github as well as in various git tools revert if the commit reverts a previous commit it should begin with revert followed by the header of the reverted commit in the body it should say this reverts commit hash where the hash is the sha of the commit being reverted type must be one of the following build changes to local repository build system and tooling ci changes to ci configuration and ci specific tooling 2 docs changes which exclusively affects documentation feat creates a new feature 1 fix fixes a previously discovered failure bug 1 perf improves performance without any change in functionality or api 1 refactor refactor without any change in functionality or api includes style changes release a release point in the repository 2 test improvements or corrections made to the project s test suite 1 this type must have a scope see the next section for more information 2 this type must not have a scope it only applies to general scripts and tooling scope the scope should be the name of the npm package affected as perceived by the person reading changelog generated from the commit messages the following is the list of supported scopes angular build angular cli angular create angular pwa angular ssr angular devkit architect angular devkit build angular angular devkit build webpack angular devkit core angular devkit schematics angular devkit schematics cli ngtools webpack schematics angular subject the subject contains succinct description of the change use the imperative present tense change not changed nor changes don t capitalize first letter be concise and direct no dot at the end examples examples of valid commit messages fix angular cli prevent the flubber from grassing refactor schematics angular move all json classes together examples of invalid commit messages fix angular cli add a new xyz command this is a feature not a fix ci angular cli fix publishing workflow the ci type cannot have a scope body just as in the subject use the imperative present tense change not changed nor changes the body should include the motivation for the change and contrast this with previous behavior footer the footer can contain information about breaking changes and deprecations it is also the place to reference github issues jira tickets and other prs that are related to this commit or that this commit will close for example breaking change breaking change summary blank line breaking change description migration instructions blank line blank line fixes issue number or deprecated what is deprecated blank line deprecation description recommended update path blank line blank line closes pr number breaking change section should start with the phrase breaking change followed by a summary of the breaking change a blank line and a detailed description of the breaking change that also includes migration instructions similarly a deprecation section should start with deprecated followed by a short description of what is deprecated a blank line and a detailed description of the deprecation that also mentions the recommended update path signing the cla please sign our contributor license agreement cla before sending pull requests for any code changes to be accepted the cla must be signed it s a quick process we promise for individuals we have a simple click through form for corporations we ll need you to print sign and one of scan email fax or mail the form spam policy see spam policy for details footer 2026 github inc footer navigation terms privacy security status community docs contact manage cookies do not share my personal information you can t perform that action at this time
|