Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 974
    • Issues 974
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 25
    • Merge requests 25
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #10706
Closed
Open
Issue created Dec 03, 2015 by bertagaz@bertagaz1 of 1 checklist item completed1/1 checklist item

Tag scenarios that rely on the shipped documentation

Originally created by @bertagaz on #10706 (Redmine)

As decided in #10492 (closed), we don’t want to run the whole test suite on branches that only change the Tails documentation, but only scenarios that relies on the documentation shipped within Tails.

The chosen implementation requires us to mark this kind of scenarios as @doc in order to do so.

Feature Branch: Tails:test/10706-add-doc-tags

Parent Task: sysadmin#10153 (closed)

Related issues

  • Blocks #10707 (closed)
  • Blocked by #10492 (closed)
Edited May 15, 2020 by bertagaz
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking