Git Product home page Git Product logo

pathspec-ruby's Issues

Problem with brackets on gitignore patter

I have a test on my pipeline for the gitignore file using the pathspec-ruby. Worked well with 0.2.1 but crashed with 1.0.0.
The error is this:

$ bundle exec rake syntax
rake aborted!
SyntaxError: /usr/local/bundle/gems/pathspec-1.0.0/lib/pathspec/gitignorespec.rb:45: syntax error, unexpected ']'
...         pattern = pattern[1..]
...                              ^
/usr/local/bundle/gems/pathspec-1.0.0/lib/pathspec/gitignorespec.rb:52: syntax error, unexpected ']'
        pattern = pattern[1..] if pattern.start_with?('\\')
                             ^
/usr/local/bundle/gems/pathspec-1.0.0/lib/pathspec.rb:1:in `require'
/usr/local/bundle/gems/pathspec-1.0.0/lib/pathspec.rb:1:in `<top (required)>'
/usr/local/bundle/gems/puppetlabs_spec_helper-2.16.0/lib/puppetlabs_spec_helper/tasks/check_symlinks.rb:3:in `require'
/usr/local/bundle/gems/puppetlabs_spec_helper-2.16.0/lib/puppetlabs_spec_helper/tasks/check_symlinks.rb:3:in `<top (required)>'
/usr/local/bundle/gems/puppetlabs_spec_helper-2.16.0/lib/puppetlabs_spec_helper/rake_tasks.rb:11:in `require'
/usr/local/bundle/gems/puppetlabs_spec_helper-2.16.0/lib/puppetlabs_spec_helper/rake_tasks.rb:11:in `<top (required)>'
/builds/equinix-mse/control-repo/Rakefile:1:in `require'
/builds/equinix-mse/control-repo/Rakefile:1:in `<top (required)>'
/usr/local/bundle/gems/rake-13.0.3/exe/rake:27:in `<top (required)>'
/usr/local/bin/bundle:23:in `load'
/usr/local/bin/bundle:23:in `<main>'

The only line with brackets on the gitignore is .*.sw[op]

Ruby 2.5.0 Support

The specs fail with this error:

3) PathSpec#match_tree unix 
     Failure/Error:
       Find.find(root) do |path|
         relpath = Pathname.new(path).relative_path_from(rootpath).to_s
         relpath += '/' if File.directory? path
         if match(relpath)
           matching << path
         end
     
     NoMethodError:
       undefined method `children' for FakeFS::Dir:Class
     # ./lib/pathspec.rb:41:in `match_tree'
     # ./spec/unit/pathspec_spec.rb:191:in `block (4 levels) in <top (required)>'
     # ./spec/unit/pathspec_spec.rb:196:in `block (4 levels) in <top (required)>'

Some missing bits according to the license

Hello,

While inspecting the codebase for preparing a debian package with it, I saw that there were some details that were missing according to the license that you've chosen for the codebase:

  • There should be a NOTICE file at the top
  • each source code file should have a short header comment that mentions the license and a copyright attribution

To find out more details about the two points, you can check out the following URL: https://infra.apache.org/apply-license.html

Release needs to happen for ~1.1.0~ 1.1.1

[x] Update changelog
[x] Ruby versions supported changed, updated minimum ruby version
[x] Some linting changes that should not effect anything
[x] tag
[x] tag again after forgetting about the allowed gem host update I did
[x] push to rubygems
[x] going to need to figure out how the new MFA based push works
[x] setup push to GH packages, as well? just going to push to rubygems at this time

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

Detected dependencies

asdf
.tool-versions
  • ruby 3.3.0
bundler
Gemfile
github-actions
.github/workflows/gem-push.yml
  • actions/checkout v4
  • ruby/setup-ruby v1
.github/workflows/ruby.yml
  • actions/checkout v4
  • ruby/setup-ruby v1
  • actions/checkout v4
  • ruby/setup-ruby v1

  • Check this box to trigger a request for Renovate to run again on this repository

Release 0.2.0

  • Bump version in gemspec and build script
  • Commit
  • Build gem, push gem
  • Tag
  • Hit release button on GH

binary file pathspec-rb is missing a man page

Hi there!

I'm currently working on packaging your gem for debian, and I was warned by the debian linting utility, lintian, that there is no man page for the binary pathspec-rb.

It's always nice to have a documentation page that one can find with man $binary to get at least a tiny bit more verbose information than the usage text.

I can try and come up with something soonish, however I'm still not yet very well acquainted with this library and its accompanying binary, so I would fear describing inaccurate information. I also don't know what formatting would be most desirable to you for the contents of the man page.

from what I can see so far, the pathspec-rb binary is a helper tool for testing matches of some values of pathspecs on a specified path. also there doesn't seem to be any configuration file involved. so the man page would probably be very simple.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.