Meta tags:
description=Send test coverage data to Coveralls.io for analysis, change tracking, and notifications;

Headings (most frequently used words):

coveralls, github, action, example, usage, demo, troubleshooting, mit, license, contributing, product, platform, support, company, inputs, outputs, standard, complete, parallel, job, steps, shown, comments, aren, added, to, my, pull, request, responds, with, cannot, find, matching, repository, verified, creator, stars, contributors, categories, links, installation,

Text of the page (most frequently used words):
#github (49), the (45), #coveralls (37), action (22), and (19), name (19), test (15), coverage (14), with (12), your (11), parallel (11), actions (10), this (9), coverallsapp (9), will (9), uses (9), you (8), token (8), all (8), node (8), optional (8), code (7), for (7), steps (7), run (7), that (6), secrets (6), runs (6), new (6), job (6), matrix (6), lcov (6), can (5), about (5), project (5), pull (5), github_token (5), pull_request (5), branch (5), build (5), master (5), latest (5), test_number (5), flag (5), version (5), file (5), jump (5), git (4), api (4), more (4), have (4), check (4), data (4), function (4), finished (4), needs (4), jobs (4), true (4), make (4), npm (4), install (4), path (4), set (4), search (4), 2022 (3), status (3), support (3), enterprise (3), security (3), open (3), verified (3), workflow (3), line (3), request (3), repo (3), push (3), added (3), results (3), commit (3), after (3), notifications (3), ubuntu (3), use (3), example (3), default (3), override (3), packages (3), info (3), suite (3), maintenance (3), marketplace (3), sign (3), signed (2), another (2), tab (2), window (2), refresh (2), session (2), reload (2), privacy (2), terms (2), blog (2), skills (2), community (2), resources (2), pricing (2), readme (2), customer (2), stories (2), features (2), product (2), not (2), documentation (2), requests (2), issues (2), links (2), review (2), learn (2), has (2), was (2), created (2), ensure (2), find (2), repository (2), comments (2), comment (2), posted (2), fail (2), create (2), details (2), first (2), changes (2), are (2), shown (2), demo (2), step (2), other (2), completed (2), sent (2), setup (2), checkout (2), complete (2), using (2), here (2), environment (2), variable (2), sha (2), hostname (2), https (2), host (2), send (2), based (2), posts (2), unique (2), required (2), into (2), need (2), when (2), analysis (2), change (2), tracking (2), release (2), source (2), manage (2), web (2), nov (2), out, perform, time, what, site, map, updated, inc, organization, tiktok, twitch, youtube, linkedin, facebook, twitter, shop, social, impact, inclusion, press, careers, company, contact, professional, services, forum, docs, desktop, electron, partners, developer, platform, roadmap, team, certified, provided, third, party, governed, separate, service, policy, report, abuse, quality, categories, contributors, 357, star, stars, creator, contributing, mit, license, yaml, matches, exactly, responds, cannot, matching, enabled, leave, setting, alerts, area, settings, page, inside, app, invited, user, collaborator, invokes, aren, troubleshooting, detailed, resulting, triggers, indicate, missing, shows, committed, pushed, without, let, know, done, aggregate, calculation, calculated, finish, strategy, assumes, building, command, nickmerwin, standard, json, response, from, url, result, outputs, github_sha, github_ref, root, folder, collected, should, used, monorepos, process, correctly, base, protocol, specifies, endpoint, last, webhook, where, multiple, performed, unit, functional, integration, local, output, produced, error, thrown, found, must, form, verify, built, does, manually, specified, store, description, requirement, inputs, outputted, most, major, runners, configured, see, usage, running, events, how, affected, merged, don, add, receiving, post, improved, parameters, choose, copy, paste, following, snippet, yml, installation, message, suggested, collections, trending, topics, repositories, articles, fund, developers, sponsors, case, studies, devsecops, devops, automation, solution, compare, startups, teams, solutions, explore, collaborate, outside, discussions, plan, track, work, write, better, copilot, instant, dev, environments, codespaces, fix, vulnerabilities, automate, any, toggle, navigation, skip, content, wayback, machine, http, archive, org, 20221128082154, com, timestamps, capture, success, 2023, 2021, dec, oct, 2019, jan, 2026, 547, captures,

Text of the page (random words):
coveralls github action actions github marketplace github 547 captures 20 nov 2019 29 jan 2026 oct nov dec 28 2021 2022 2023 success fail about this capture timestamps the wayback machine http web archive org web 20221128082154 https github com marketplace actions coveralls github action skip to content toggle navigation sign up product actions automate any workflow packages host and manage packages security find and fix vulnerabilities codespaces instant dev environments copilot write better code with ai code review manage code changes issues plan and track work discussions collaborate outside of code explore all features documentation github skills blog solutions for enterprise teams startups compare all by solution ci cd automation devops devsecops case studies customer stories resources open source github sponsors fund open source developers the readme project github community articles repositories topics trending collections pricing search all github jump to no suggested jump to results search all github jump to search all github jump to search all github jump to sign in sign up message marketplace actions coveralls github action coverallsapp github action coveralls github action 1 1 3 latest version use latest version coverallsapp coveralls github action send test coverage data to coveralls io for analysis change tracking and notifications installation copy and paste the following snippet into your yml file name coveralls github action uses coverallsapp github action 1 1 3 learn more about this action in coverallsapp github action choose a version 1 1 3 git branch sha override parameters and security maintenance v1 1 2 maintenance release v1 1 1 maintenance release v1 1 0 improved parallel job support v1 0 1 coveralls github action this github action posts your test suite s lcov coverage data to coveralls io for analysis change tracking and notifications you don t need to add the repo to coveralls first it will be created when receiving the post when running on pull_request events a comment will be added to the pr with details about how coverage will be affected if merged usage the action s step needs to run after your test suite has outputted an lcov file most major test runners can be configured to do so if you re using node see more info here inputs name requirement description github token required must be in form github token secrets github_token coveralls uses this token to verify the posted coverage data on the repo and create a new check based on the results it is built into github actions and does not need to be manually specified in your secrets store more info path to lcov optional default coverage lcov info local path to the lcov output file produced by your test suite an error will be thrown if the file can t be found this is the file that will be sent to the coveralls api flag name optional unique required if parallel job flag name e g unit functional or integration will be shown in the coveralls ui parallel optional set to true for parallel or matrix based steps where multiple posts to coveralls will be performed in the check flag name needs to be set and unique e g flag name run matrix test_number parallel finished optional set to true in the last job after the other parallel jobs steps have completed this will send a webhook to coveralls to set the build complete coveralls endpoint optional hostname and protocol https host specifies a coveralls enterprise hostname base path optional path to the root folder of the project the coverage was collected in should be used in monorepos so that coveralls can process the lcov correctly e g packages my project git branch optional default github_ref environment variable override the branch name git commit optional default github_sha environment variable override the commit sha outputs coveralls api result json response from the coveralls api with a status code and url for the job on coveralls standard example this example assumes you re building a node project using the command make test coverage demo here nickmerwin node coveralls on push pull_request name test coveralls jobs build name build runs on ubuntu latest steps uses actions checkout v1 name use node js 10 x uses actions setup node v1 with node version 10 x name npm install make test coverage run npm install make test coverage name coveralls uses coverallsapp github action master with github token secrets github_token complete parallel job example on push pull_request name test coveralls parallel jobs test runs on ubuntu latest strategy matrix test_number 1 2 steps uses actions checkout master name use node js 10 x uses actions setup node master with version 10 x name npm install run npm install name test matrix test_number run make test coverage matrix test_number name coveralls parallel uses coverallsapp github action master with github token secrets github_token flag name run matrix test_number parallel true finish needs test runs on ubuntu latest steps name coveralls finished uses coverallsapp github action master with github token secrets github_token parallel finished true the coveralls finished step needs to run after all other steps have completed it will let coveralls know that all jobs in the build are done and aggregate coverage calculation can be calculated and notifications sent demo steps shown a new function f without test coverage is added the changes are committed and pushed to a new branch function f the action runs on github ci the commit on github shows a new check for coveralls with details first build on function f at 92 0 and links to the job on coveralls line by line results indicate the new function is missing coverage create a pull request with the new branch the pull_request check runs and the resulting coverage data triggers a fail status a detailed comment is posted troubleshooting coveralls comments aren t added to my pull request ensure that your workflow invokes the coveralls action runs on pull requests e g on push pull_request you have invited the coveralls user to your repository as a collaborator you have enabled the leave comments setting in the pull request alerts area in your repo settings page inside the coveralls app coveralls responds with cannot find matching repository ensure your workflow yaml line for the github token matches exactly github token secrets github_token mit license contributing verified creator github has verified that this action was created by coverallsapp learn more about verified actions stars star 357 contributors categories code review code quality links coverallsapp github action open issues 57 pull requests 19 report abuse coveralls github action is not certified by github it is provided by a third party and is governed by separate terms of service privacy policy and support documentation product features security team enterprise customer stories the readme project pricing resources roadmap platform developer api partners electron github desktop support docs community forum professional services skills status contact github company about blog careers press inclusion social impact shop github on twitter github on facebook github on linkedin github on youtube github on twitch github on tiktok github s organization on github 2022 github inc terms privacy updated 08 2022 site map what is git you can t perform that action at this time 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