checkoff 0.222.0 → 0.225.0

data/.gitattributes

@@ -1,6 +0,0 @@
-# there's a lot of .sh in the build machinery; this can overwhelm
-# smaller projects and confuse GitHub's detection of majority project
-# type (GitHub uses the linguist library)
-#
-# https://dev.to/katkelly/changing-your-repo-s-language-in-github-5gjo
-*.sh linguist-detectable=false

data/.gitignore

@@ -1,61 +0,0 @@
-# OSX useful to ignore
-*.DS_Store
-.AppleDouble
-.LSOverride
-
-# Thumbnails
-._*
-
-# Files that might appear in the root of a volume
-.DocumentRevisions-V100
-.fseventsd
-.Spotlight-V100
-.TemporaryItems
-.Trashes
-.VolumeIcon.icns
-.com.apple.timemachine.donotpresent
-
-# Directories potentially created on remote AFP share
-.AppleDB
-.AppleDesktop
-Network Trash Folder
-Temporary Items
-.apdisk
-
-# IntelliJ Idea family of suites
-.idea
-*.iml
-## File-based project format:
-*.ipr
-*.iws
-## mpeltonen/sbt-idea plugin
-.idea_modules/
-
-# IDE settings
-.vscode/
-
-# Editor temp files
-*~
-\#*\#
-
-# Used by Makefile to track what we have and haven't installed
-Gemfile.lock.installed
-requirements_dev.txt.installed
-types.installed
-
-# Used by CircleCI as a place to store installed gems
-/vendor
-
-# Installed by fix.sh based on what latest versions are
-/.python-version
-/.ruby-version
-
-# Ruby-related
-/.bundle/
-/.yardoc
-/_yardoc/
-/doc/
-/pkg/
-/spec/reports/
-/tmp/
-/coverage/

data/.markdownlint_style.rb

@@ -1,3 +0,0 @@
-# frozen_string_literal: true
-
-rule 'MD029', style: 'ordered'

data/.mdlrc

@@ -1 +0,0 @@
-style ".markdownlint_style.rb"

data/.overcommit.yml

@@ -1,114 +0,0 @@
----
-# Use this file to configure the Overcommit hooks you wish to use. This will
-# extend the default configuration defined in:
-# https://github.com/sds/overcommit/blob/master/config/default.yml
-#
-# At the topmost level of this YAML file is a key representing type of hook
-# being run (e.g. pre-commit, commit-msg, etc.). Within each type you can
-# customize each hook, such as whether to only run it on certain files (via
-# `include`), whether to only display output if it fails (via `quiet`), etc.
-#
-# For a complete list of hooks, see:
-# https://github.com/sds/overcommit/tree/master/lib/overcommit/hook
-#
-# For a complete list of options that you can use to customize hooks, see:
-# https://github.com/sds/overcommit#configuration
-#
-# Uncomment the following lines to make the configuration take effect.
-
-PreCommit:
-  # Extend default config at
-  # https://github.com/sds/overcommit/blob/master/config/default.yml
-  BrokenSymlinks:
-    enabled: true
-    description: 'Check for broken symlinks'
-    quiet: true
-  RuboCop:
-    enabled: true
-    command: ['bundle', 'exec', 'rubocop']
-    include:
-      - '**/*.gemspec'
-      - '**/*.rake'
-      - '**/*.rb'
-      - '**/*.ru'
-      - '**/Gemfile'
-      - '**/Rakefile'
-      - 'bin/*'
-      - 'exe/*'
-      - 'script/*'
-    problem_on_unmodified_line: warn
-    exclude:
-      - db/migrate/*.rb
-      - db/schema.rb
-  PythonFlake8:
-    enabled: true
-    on_warn: fail
-  ShellCheck:
-    enabled: true
-    on_warn: fail
-    include:
-      - '.envrc'
-      - '**/*.sh'
-  YamlLint:
-    enabled: true
-    flags: ['-c', '.yamllint.yml', '--format=parsable', '--strict']
-    on_warn: fail
-    exclude:
-      - '.rubocop_todo.yml' # generated
-      - 'sorbet/**/*' # generated
-  CircleCi:
-    required_executable: 'circleci'
-    flags: ['config', 'validate']
-    include:
-      - '.circleci/config.yml'
-    enabled: true
-  SolargraphTypecheck:
-    enabled: true
-    problem_on_unmodified_line: warn
-    include:
-      # process first
-      - "config/annotations*.rb"
-      - "**/*.rb"
-      - "**/.*.rb"
-      - "lib/tasks/*.rake"
-      - ".git-hooks/**/*.rb"
-      - "script/*"
-      - "bin/*"
-      - "bin/overcommit_branch"
-    exclude:
-      - script/.rubocop.yml
-      - vendor/**/*
-      - spec/**/*
-      - feature/**/*
-      - test/**/*
-      - ".bundle/**/*"
-      - ".markdownlint_style.rb"
-  Sorbet:
-    enabled: true
-  Punchlist:
-    command: ['bundle', 'exec', 'punchlist']
-    enabled: true
-    problem_on_unmodified_line: warn
-    exclude:
-      - 'sorbet/**/*'
-
-PrePush:
-  Brakeman:
-    enabled: true
-    flags: ['--exit-on-warn', '--quiet', '--summary', '--force']
-  RakeTarget:
-    enabled: true
-    command: ['bundle', 'exec', 'rake']
-    include:
-      - 'Rakefile'
-    targets:
-      - 'clear_metrics'
-      - 'test'
-      - 'undercover'
-
-#PostCheckout:
-#  ALL: # Special hook name that customizes all hooks of this type
-#    quiet: true # Change all post-checkout hooks to only display output on failure
-#
-#  IndexTags:
-#    enabled: true # Generate a tags file with `ctags` each time HEAD changes

data/.rubocop.yml

@@ -1,143 +0,0 @@
----
-inherit_from: .rubocop_todo.yml
-
-Gemspec/RequireMFA:
-  # We publish via CI/CD, so MFA is not possible.
-  Enabled: false
-
-Layout/LineLength:
-  Max: 120
-
-Layout/MultilineMethodCallIndentation:
-  EnforcedStyle: indented
-
-Lint/EmptyClass:
-  # some workarounds for circular dependencies require empty classes
-  AllowComments: true
-
-# conflicts with solargraph wanting every parameter documented with
-# actual name and subclassing
-Lint/UnusedMethodArgument:
-  Enabled: false
-
-# https://stackoverflow.com/questions/40934345/rubocop-25-line-block-size-and-rspec-tests
-Metrics/BlockLength:
-  # Exclude DSLs
-  Exclude:
-    - 'Rakefile'
-    - '*.gemspec'
-    - '**/*.rake'
-    - 'spec/**/*.rb'
-    - 'feature/**/*.rb'
-
-# I use keyword arguments for a poor man's dependency injection to cut
-# down on the magic in my tests.
-Metrics/ParameterLists:
-  CountKeywordArgs: false
-
-# Can try removing this after I have a release installed with this
-# fix (probably in rubocop-minitest 0.10.3):
-#
-# https://github.com/rubocop-hq/rubocop-minitest/pull/116
-Minitest/TestMethodName:
-  Enabled: false
-
-Naming/FileName:
-  Exclude:
-    - 'lib/checkoff.rb'
-
-Naming/HeredocDelimiterNaming:
-  Enabled: false
-
-Naming/MethodParameterName:
-  Enabled: true
-  AllowedNames:
-    # I don't think things on this list are a terribly hard convention
-    # for folks to learn.  bbatsov also doesn't care much for this
-    # check:
-    #
-    # https://github.com/rubocop-hq/rubocop/issues/3666
-    - e # exception
-    - x # cartesian coordinates
-    - y # cartesian coordinates
-    - n # number of things
-
-# by default (EnforcedStyle=NormalCase) this rule doesn't like
-# things like check_1, check_2, etc and wants check1, check2, etc. I
-# like the former.
-#
-# https://docs.rubocop.org/rubocop/cops_naming.html#namingvariablenumber
-Naming/VariableNumber:
-  Enabled: true
-  EnforcedStyle: snake_case
-
-#
-# Add 'XX X' to the standard list
-#
-Style/CommentAnnotation:
-  Keywords:
-    - "TOD\
-       O"
-    - "FIXM\
-       E"
-    - "OPTIMIZ\
-       E"
-    - "HAC\
-       K"
-    - "REVIE\
-       W"
-    - "XX\
-       X"
-
-Style/DocumentationMethod:
-  Enabled: true
-  Include:
-    - 'lib/checkoff/*.rb'
-
-Style/StringLiterals:
-  EnforcedStyle: single_quotes
-  SupportedStyles:
-    - single_quotes
-    - double_quotes
-  ConsistentQuotesInMultiline: true
-
-# Solargraph needs to see a class inherited from Struct to recognize
-# what's going on
-Style/StructInheritance:
-  Enabled: false
-
-# I like trailing commas in arrays and hashes.  They let me insert new
-# elements and see them as one line in a diff, not two.
-Style/TrailingCommaInArrayLiteral:
-  EnforcedStyleForMultiline: comma
-
-Style/TrailingCommaInHashLiteral:
-  EnforcedStyleForMultiline: comma
-
-# If I'm using one function name and returning the contents of an
-# attribute, that's OK.  The alternative would be this, which I find
-# confusing and often not really what I mean:
-#
-# attr_reader :something_else
-# alias_method :something, :something_else
-Style/TrivialAccessors:
-  ExactNameMatch: true
-
-Lint:
-  Severity: error
-
-Metrics:
-  Severity: error
-
-AllCops:
-  NewCops: enable
-  TargetRubyVersion: 3.0
-  Exclude:
-    - 'bin/*'
-    - 'vendor/**/*'
-    - 'sorbet/**/*'
-
-require:
-  - rubocop-minitest
-  - rubocop-performance
-  - rubocop-rake

data/.rubocop_todo.yml

@@ -1,90 +0,0 @@
-# This configuration was generated by
-# `rubocop --auto-gen-config --auto-gen-only-exclude --no-exclude-limit --no-auto-gen-timestamp`
-# using RuboCop version 1.59.0.
-# The point is for the user to remove these configuration records
-# one by one as the offenses are removed from the code base.
-# Note that changes in the inspected code, or installation of new
-# versions of RuboCop, may require this file to be generated again.
-
-# Offense count: 21
-# Configuration parameters: AllowedMethods, AllowedPatterns, CountRepeatedAttributes, Max.
-Metrics/AbcSize:
-  Exclude:
-    - 'lib/checkoff/internal/asana_event_filter.rb'
-    - 'lib/checkoff/task_searches.rb'
-    - 'lib/checkoff/tasks.rb'
-    - 'lib/checkoff/timelines.rb'
-    - 'test/unit/test_portfolios.rb'
-    - 'test/unit/test_task_selectors.rb'
-    - 'test/unit/test_tasks.rb'
-    - 'test/unit/test_timelines.rb'
-
-# Offense count: 9
-# Configuration parameters: CountComments, Max, CountAsOne.
-Metrics/ClassLength:
-  Exclude:
-    - 'lib/checkoff/attachments.rb'
-    - 'lib/checkoff/custom_fields.rb'
-    - 'lib/checkoff/projects.rb'
-    - 'lib/checkoff/sections.rb'
-    - 'lib/checkoff/tasks.rb'
-    - 'lib/checkoff/timing.rb'
-    - 'test/unit/test_sections.rb'
-    - 'test/unit/test_tasks.rb'
-    - 'test/unit/test_timelines.rb'
-
-# Offense count: 4
-# Configuration parameters: AllowedMethods, AllowedPatterns, Max.
-Metrics/CyclomaticComplexity:
-  Exclude:
-    - 'lib/checkoff/internal/asana_event_filter.rb'
-    - 'lib/checkoff/internal/task_timing.rb'
-    - 'lib/checkoff/timelines.rb'
-
-# Offense count: 12
-# Configuration parameters: CountComments, Max, CountAsOne, AllowedMethods, AllowedPatterns.
-Metrics/MethodLength:
-  Exclude:
-    - 'lib/checkoff/attachments.rb'
-    - 'lib/checkoff/internal/asana_event_filter.rb'
-    - 'lib/checkoff/internal/search_url/date_param_converter.rb'
-    - 'lib/checkoff/my_tasks.rb'
-    - 'lib/checkoff/task_searches.rb'
-    - 'lib/checkoff/tasks.rb'
-    - 'lib/checkoff/timelines.rb'
-    - 'lib/checkoff/timing.rb'
-
-# Offense count: 2
-# Configuration parameters: AllowedMethods, AllowedPatterns, Max.
-Metrics/PerceivedComplexity:
-  Exclude:
-    - 'lib/checkoff/timelines.rb'
-
-# Offense count: 2
-# Configuration parameters: MinSize.
-Performance/CollectionLiteralInLoop:
-  Exclude:
-    - 'lib/checkoff/tasks.rb'
-    - 'test/unit/test_helper.rb'
-
-# Offense count: 1
-# This cop supports unsafe autocorrection (--autocorrect-all).
-Performance/InefficientHashSearch:
-  Exclude:
-    - 'lib/checkoff/internal/asana_event_filter.rb'
-
-# Offense count: 1
-# This cop supports unsafe autocorrection (--autocorrect-all).
-# Configuration parameters: AllowRegexpMatch.
-Performance/RedundantEqualityComparisonBlock:
-  Exclude:
-    - 'lib/checkoff/internal/selector_classes/task.rb'
-
-# Offense count: 10
-# Configuration parameters: RequireForNonPublicMethods.
-Style/DocumentationMethod:
-  Exclude:
-    - 'spec/**/*'
-    - 'test/**/*'
-    - 'lib/checkoff/cli.rb'
-    - 'lib/checkoff/tags.rb'

data/.solargraph.yml

@@ -1,35 +0,0 @@
----
-include:
-  # process first
-  - "config/annotations*.rb"
-  - "**/*.rb"
-  - "**/.*.rb"
-  - "lib/tasks/*.rake"
-  - ".git-hooks/**/*.rb"
-  - "script/*"
-  - "bin/*"
-  - "bin/overcommit_branch"
-exclude:
-  - script/.rubocop.yml
-  - vendor/**/*
-  - spec/**/*
-  - feature/**/*
-  - test/**/*
-  - ".bundle/**/*"
-  - ".markdownlint_style.rb"
-require: []
-domains: []
-reporters:
-  - rubocop
-  - require_not_found
-  - typecheck:strong
-  - update_errors
-formatter:
-  rubocop:
-    cops: safe
-    except: []
-    only: []
-    extra_args: []
-require_paths: []
-plugins: []
-max_files: 5000

data/.yamllint.yml

@@ -1,8 +0,0 @@
----
-# https://yamllint.readthedocs.io/en/stable/configuration.html
-extends: default
-
-rules:
-  comments: disable
-  line-length:
-    max: 120

data/CODE_OF_CONDUCT.md

@@ -1,133 +0,0 @@
-
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-We as members, contributors, and leaders pledge to make participation in our
-community a harassment-free experience for everyone, regardless of age, body
-size, visible or invisible disability, ethnicity, sex characteristics, gender
-identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, caste, color, religion, or sexual identity
-and orientation.
-
-We pledge to act and interact in ways that contribute to an open, welcoming,
-diverse, inclusive, and healthy community.
-
-## Our Standards
-
-Examples of behavior that contributes to a positive environment for our
-community include:
-
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes,
-  and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the
-  overall community
-
-Examples of unacceptable behavior include:
-
-* The use of sexualized language or imagery, and sexual attention or
-  advances of any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email
-  address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Enforcement Responsibilities
-
-Community leaders are responsible for clarifying and enforcing our standards of
-acceptable behavior and will take appropriate and fair corrective action in
-response to any behavior that they deem inappropriate, threatening, offensive,
-or harmful.
-
-Community leaders have the right and responsibility to remove, edit, or reject
-comments, commits, code, wiki edits, issues, and other contributions that are
-not aligned to this Code of Conduct, and will communicate reasons for moderation
-decisions when appropriate.
-
-## Scope
-
-This Code of Conduct applies within all community spaces, and also applies when
-an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official e-mail address,
-posting via an official social media account, or acting as an appointed
-representative at an online or offline event.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at
-[INSERT CONTACT METHOD].
-All complaints will be reviewed and investigated promptly and fairly.
-
-All community leaders are obligated to respect the privacy and security of the
-reporter of any incident.
-
-## Enforcement Guidelines
-
-Community leaders will follow these Community Impact Guidelines in determining
-the consequences for any action they deem in violation of this Code of Conduct:
-
-### 1. Correction
-
-**Community Impact**: Use of inappropriate language or other behavior deemed
-unprofessional or unwelcome in the community.
-
-**Consequence**: A private, written warning from community leaders, providing
-clarity around the nature of the violation and an explanation of why the
-behavior was inappropriate. A public apology may be requested.
-
-### 2. Warning
-
-**Community Impact**: A violation through a single incident or series
-of actions.
-
-**Consequence**: A warning with consequences for continued behavior. No
-interaction with the people involved, including unsolicited interaction with
-those enforcing the Code of Conduct, for a specified period of time. This
-includes avoiding interactions in community spaces as well as external channels
-like social media. Violating these terms may lead to a temporary or
-permanent ban.
-
-### 3. Temporary Ban
-
-**Community Impact**: A serious violation of community standards, including
-sustained inappropriate behavior.
-
-**Consequence**: A temporary ban from any sort of interaction or public
-communication with the community for a specified period of time. No public or
-private interaction with the people involved, including unsolicited interaction
-with those enforcing the Code of Conduct, is allowed during this period.
-Violating these terms may lead to a permanent ban.
-
-### 4. Permanent Ban
-
-**Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior,  harassment of an
-individual, or aggression toward or disparagement of classes of individuals.
-
-**Consequence**: A permanent ban from any sort of public interaction within
-the community.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.0, available at
-[https://www.contributor-covenant.org/version/2/0/code_of_conduct.html][v2.0].
-
-Community Impact Guidelines were inspired by
-[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
-
-For answers to common questions about this code of conduct, see the FAQ at
-[https://www.contributor-covenant.org/faq][FAQ]. Translations are available
-at [https://www.contributor-covenant.org/translations][translations].
-
-[homepage]: https://www.contributor-covenant.org
-[v2.0]: https://www.contributor-covenant.org/version/2/0/code_of_conduct.html
-[Mozilla CoC]: https://github.com/mozilla/diversity
-[FAQ]: https://www.contributor-covenant.org/faq
-[translations]: https://www.contributor-covenant.org/translations

data/CONTRIBUTING.rst

@@ -1,75 +0,0 @@
-============
-Contributing
-============
-
-Contributions are welcome, and they are greatly appreciated! Every little bit
-helps, and credit will always be given.
-
-You can contribute in many ways:
-
-Types of Contributions
-----------------------
-
-Report Bugs
-~~~~~~~~~~~
-
-Report bugs at https://github.com/apiology/checkoff/issues
-
-If you are reporting a bug, please include:
-
-* Your operating system name and version.
-* Any details about your local setup that might be helpful in troubleshooting.
-* Detailed steps to reproduce the bug.
-
-Fix Bugs
-~~~~~~~~
-
-Look through the GitHub issues for bugs. Anything tagged with "bug"
-and "help wanted" is open to whoever wants to implement a fix for it.
-
-Implement Features
-~~~~~~~~~~~~~~~~~~
-
-Look through the GitHub issues for features. Anything tagged with "enhancement"
-and "help wanted" is open to whoever wants to implement it.
-
-If you have a new feature in mind, please start it by filing an issue
-so we can discuss the need and approach before you invest time into
-coding it.
-
-Write Documentation
-~~~~~~~~~~~~~~~~~~~
-
-Checkoff could always use more documentation, whether as part of
-the official Checkoff docs, in docstrings, or even on the web in blog posts, articles,
-and such.
-
-Submit Feedback
-~~~~~~~~~~~~~~~
-
-The best way to send feedback is to file an issue at
-https://github.com/apiology/checkoff/issues.
-
-If you are proposing a new feature:
-
-* Explain in detail how it would work.
-* Keep the scope as narrow as possible, to make it easier to implement.
-* Remember that this is a volunteer-driven project, and that contributions
-  are welcome :)
-
-Get Started!
-------------
-
-Ready to contribute?  See DEVELOPMENT.md in this directory for details
-on how to set yourself up for local development.
-
-Pull Request Guidelines
------------------------
-
-Before you submit a pull request, check that it meets these guidelines:
-
-1. The pull request should include tests.
-
-2. If the pull request adds functionality, the docs should be updated. Put your
-   new functionality into a function with a docstring, and add the feature to
-   the list in README.md.