k_fileset 0.0.3
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +7 -0
- data/.github/workflows/main.yml +31 -0
- data/.gitignore +50 -0
- data/.rspec +3 -0
- data/.rubocop.yml +93 -0
- data/CODE_OF_CONDUCT.md +74 -0
- data/Gemfile +25 -0
- data/Guardfile +30 -0
- data/LICENSE.txt +21 -0
- data/README.md +89 -0
- data/Rakefile +33 -0
- data/STORIES.md +52 -0
- data/USAGE.md +19 -0
- data/bin/console +16 -0
- data/bin/k +36 -0
- data/bin/kgitsync +76 -0
- data/bin/khotfix +244 -0
- data/bin/setup +11 -0
- data/hooks/pre-commit +87 -0
- data/hooks/update-version +33 -0
- data/k_fileset.gemspec +44 -0
- data/lib/k_fileset/file_set.rb +195 -0
- data/lib/k_fileset/file_set_examples.rb +64 -0
- data/lib/k_fileset/glob_entry.rb +57 -0
- data/lib/k_fileset/glob_info.rb +55 -0
- data/lib/k_fileset/glob_props.rb +10 -0
- data/lib/k_fileset/path_entry.rb +141 -0
- data/lib/k_fileset/version.rb +5 -0
- data/lib/k_fileset/whitelist.rb +62 -0
- data/lib/k_fileset.rb +24 -0
- metadata +90 -0
checksums.yaml
ADDED
@@ -0,0 +1,7 @@
|
|
1
|
+
---
|
2
|
+
SHA256:
|
3
|
+
metadata.gz: f0c6ebc81463c4886df159ad4e39c821d1a9affc9805ddc1842f30cc3c7a6db9
|
4
|
+
data.tar.gz: e86c18d57611ed75f718382d21ad3587da1744a4fff0e0d59528c245d6e29597
|
5
|
+
SHA512:
|
6
|
+
metadata.gz: 8d6d7e7fa4e16bb8ddfcc09af65eff8b2fef7d77ea3d5375c29d54bf0490c8936ba975e46125a9595cd767c6a3b38602168c0c728410a6856b053162ddb14e4a
|
7
|
+
data.tar.gz: 44e0430b450557ed803767c0e6d9d825792f6bf9572df6eae39d83027c75f2c7c5838fe93305681724c84d9aa94ddb11805ebb8c36cbc6c78a7ebce49824d20c
|
@@ -0,0 +1,31 @@
|
|
1
|
+
# This workflow will download a prebuilt Ruby version, install dependencies and run tests with Rake
|
2
|
+
# For more information see: https://github.com/marketplace/actions/setup-ruby-jruby-and-truffleruby
|
3
|
+
name: Ruby
|
4
|
+
|
5
|
+
on:
|
6
|
+
push:
|
7
|
+
branches: [ master ]
|
8
|
+
pull_request:
|
9
|
+
branches: [ master ]
|
10
|
+
|
11
|
+
jobs:
|
12
|
+
test:
|
13
|
+
|
14
|
+
runs-on: ubuntu-latest
|
15
|
+
|
16
|
+
steps:
|
17
|
+
- uses: actions/checkout@v2
|
18
|
+
- name: Set up Ruby
|
19
|
+
# To automatically get bug fixes and new Ruby versions for ruby/setup-ruby,
|
20
|
+
# change this to (see https://github.com/ruby/setup-ruby#versioning):
|
21
|
+
uses: ruby/setup-ruby@v1
|
22
|
+
with:
|
23
|
+
ruby-version: 2.7.1
|
24
|
+
- name: Install dependencies
|
25
|
+
run: |
|
26
|
+
gem install bundler -v 2.2.5
|
27
|
+
bundle install
|
28
|
+
- name: Run tests
|
29
|
+
run: bundle exec rspec
|
30
|
+
- name: Run rubocop
|
31
|
+
run: bundle exec rubocop
|
data/.gitignore
ADDED
@@ -0,0 +1,50 @@
|
|
1
|
+
# Move this into a KLUE SATELITE DOCUMENT
|
2
|
+
# See https://help.github.com/articles/ignoring-files for more about ignoring files.
|
3
|
+
#
|
4
|
+
# If you find yourself ignoring temporary files generated by your text editor
|
5
|
+
# or operating system, you probably want to add a global ignore instead:
|
6
|
+
# git config --global core.excludesfile '~/.gitignore_global'
|
7
|
+
#
|
8
|
+
# The Octocat has a Gist containing some good rules to add to this file.
|
9
|
+
# https://gist.github.com/octocat/9257657
|
10
|
+
|
11
|
+
# Ignore Klue Setup.sh
|
12
|
+
/bin/runonce/
|
13
|
+
k_fileset.yml
|
14
|
+
|
15
|
+
/_/
|
16
|
+
/.bundle/
|
17
|
+
/.history/
|
18
|
+
/.yardoc
|
19
|
+
/_yardoc/
|
20
|
+
/coverage/
|
21
|
+
/log/
|
22
|
+
!/log/.keep
|
23
|
+
/doc/
|
24
|
+
/pkg/
|
25
|
+
/spec/reports/
|
26
|
+
/tmp/
|
27
|
+
!/tmp/.keep
|
28
|
+
*.bundle
|
29
|
+
*.so
|
30
|
+
*.o
|
31
|
+
*.a
|
32
|
+
mkmf.log
|
33
|
+
|
34
|
+
# Ruby Version
|
35
|
+
.ruby-version
|
36
|
+
|
37
|
+
# Environment File
|
38
|
+
.env
|
39
|
+
|
40
|
+
# Gems should not use a Gemfile.lock
|
41
|
+
Gemfile.lock
|
42
|
+
|
43
|
+
# RubyGem definitions
|
44
|
+
*.gem
|
45
|
+
|
46
|
+
# rspec failure tracking
|
47
|
+
.rspec_status
|
48
|
+
|
49
|
+
# ByeBug history
|
50
|
+
.byebug_history
|
data/.rspec
ADDED
data/.rubocop.yml
ADDED
@@ -0,0 +1,93 @@
|
|
1
|
+
AllCops:
|
2
|
+
TargetRubyVersion: 2.5
|
3
|
+
DisplayCopNames: true
|
4
|
+
ExtraDetails: true
|
5
|
+
NewCops: enable
|
6
|
+
Exclude:
|
7
|
+
- "_/**/*"
|
8
|
+
- "spec/samples/**/*"
|
9
|
+
|
10
|
+
Metrics/BlockLength:
|
11
|
+
Exclude:
|
12
|
+
- "**/spec/**/*"
|
13
|
+
- "*.gemspec"
|
14
|
+
IgnoredMethods:
|
15
|
+
- configure
|
16
|
+
- context
|
17
|
+
- define
|
18
|
+
- describe
|
19
|
+
- draw
|
20
|
+
- factory
|
21
|
+
- feature
|
22
|
+
- guard
|
23
|
+
- included
|
24
|
+
- it
|
25
|
+
- let
|
26
|
+
- let!
|
27
|
+
- scenario
|
28
|
+
- setup
|
29
|
+
- shared_context
|
30
|
+
- shared_examples
|
31
|
+
- shared_examples_for
|
32
|
+
- transaction
|
33
|
+
|
34
|
+
Metrics/AbcSize:
|
35
|
+
Exclude:
|
36
|
+
- "**/spec/**/*"
|
37
|
+
|
38
|
+
Metrics/CyclomaticComplexity:
|
39
|
+
Exclude:
|
40
|
+
- "**/spec/**/*"
|
41
|
+
|
42
|
+
Metrics/PerceivedComplexity:
|
43
|
+
Exclude:
|
44
|
+
- "**/spec/**/*"
|
45
|
+
|
46
|
+
Metrics/MethodLength:
|
47
|
+
Max: 25
|
48
|
+
|
49
|
+
Layout/LineLength:
|
50
|
+
Max: 200
|
51
|
+
# Ignores annotate output
|
52
|
+
IgnoredPatterns: ['\A# \*\*']
|
53
|
+
IgnoreCopDirectives: true
|
54
|
+
|
55
|
+
Lint/UnusedMethodArgument:
|
56
|
+
AllowUnusedKeywordArguments: true
|
57
|
+
|
58
|
+
Style/BlockComments:
|
59
|
+
Enabled: false
|
60
|
+
Include:
|
61
|
+
- "**/spec/*"
|
62
|
+
|
63
|
+
# My Preferences - Start
|
64
|
+
Metrics/ClassLength:
|
65
|
+
Enabled: false
|
66
|
+
Metrics/ModuleLength:
|
67
|
+
Exclude:
|
68
|
+
- "**/spec/**/*"
|
69
|
+
Naming/MemoizedInstanceVariableName:
|
70
|
+
Enabled: false
|
71
|
+
Naming/VariableNumber:
|
72
|
+
Exclude:
|
73
|
+
- "**/spec/**/*"
|
74
|
+
Style/EmptyMethod:
|
75
|
+
Exclude:
|
76
|
+
- "**/spec/**/*"
|
77
|
+
Metrics/ParameterLists:
|
78
|
+
Exclude:
|
79
|
+
- "**/spec/**/*"
|
80
|
+
Layout/EmptyLineBetweenDefs:
|
81
|
+
Exclude:
|
82
|
+
- "**/spec/**/*"
|
83
|
+
|
84
|
+
Lint/AmbiguousBlockAssociation:
|
85
|
+
Exclude:
|
86
|
+
- "**/spec/**/*"
|
87
|
+
|
88
|
+
Style/AccessorGrouping:
|
89
|
+
Enabled: false
|
90
|
+
|
91
|
+
Layout/SpaceBeforeComma:
|
92
|
+
Enabled: false
|
93
|
+
# My Preferences - End
|
data/CODE_OF_CONDUCT.md
ADDED
@@ -0,0 +1,74 @@
|
|
1
|
+
# Contributor Covenant Code of Conduct
|
2
|
+
|
3
|
+
## Our Pledge
|
4
|
+
|
5
|
+
In the interest of fostering an open and welcoming environment, we as
|
6
|
+
contributors and maintainers pledge to making participation in our project and
|
7
|
+
our community a harassment-free experience for everyone, regardless of age, body
|
8
|
+
size, disability, ethnicity, gender identity and expression, level of experience,
|
9
|
+
nationality, personal appearance, race, religion, or sexual identity and
|
10
|
+
orientation.
|
11
|
+
|
12
|
+
## Our Standards
|
13
|
+
|
14
|
+
Examples of behavior that contributes to creating a positive environment
|
15
|
+
include:
|
16
|
+
|
17
|
+
- Using welcoming and inclusive language
|
18
|
+
- Being respectful of differing viewpoints and experiences
|
19
|
+
- Gracefully accepting constructive criticism
|
20
|
+
- Focusing on what is best for the community
|
21
|
+
- Showing empathy towards other community members
|
22
|
+
|
23
|
+
Examples of unacceptable behavior by participants include:
|
24
|
+
|
25
|
+
- The use of sexualized language or imagery and unwelcome sexual attention or
|
26
|
+
advances
|
27
|
+
- Trolling, insulting/derogatory comments, and personal or political attacks
|
28
|
+
- Public or private harassment
|
29
|
+
- Publishing others' private information, such as a physical or electronic
|
30
|
+
address, without explicit permission
|
31
|
+
- Other conduct which could reasonably be considered inappropriate in a
|
32
|
+
professional setting
|
33
|
+
|
34
|
+
## Our Responsibilities
|
35
|
+
|
36
|
+
Project maintainers are responsible for clarifying the standards of acceptable
|
37
|
+
behavior and are expected to take appropriate and fair corrective action in
|
38
|
+
response to any instances of unacceptable behavior.
|
39
|
+
|
40
|
+
Project maintainers have the right and responsibility to remove, edit, or
|
41
|
+
reject comments, commits, code, wiki edits, issues, and other contributions
|
42
|
+
that are not aligned to this Code of Conduct, or to ban temporarily or
|
43
|
+
permanently any contributor for other behaviors that they deem inappropriate,
|
44
|
+
threatening, offensive, or harmful.
|
45
|
+
|
46
|
+
## Scope
|
47
|
+
|
48
|
+
This Code of Conduct applies both within project spaces and in public spaces
|
49
|
+
when an individual is representing the project or its community. Examples of
|
50
|
+
representing a project or community include using an official project e-mail
|
51
|
+
address, posting via an official social media account, or acting as an appointed
|
52
|
+
representative at an online or offline event. Representation of a project may be
|
53
|
+
further defined and clarified by project maintainers.
|
54
|
+
|
55
|
+
## Enforcement
|
56
|
+
|
57
|
+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
|
58
|
+
reported by contacting the project team at david.cruwys@bugcrowd.com. All
|
59
|
+
complaints will be reviewed and investigated and will result in a response that
|
60
|
+
is deemed necessary and appropriate to the circumstances. The project team is
|
61
|
+
obligated to maintain confidentiality with regard to the reporter of an incident.
|
62
|
+
Further details of specific enforcement policies may be posted separately.
|
63
|
+
|
64
|
+
Project maintainers who do not follow or enforce the Code of Conduct in good
|
65
|
+
faith may face temporary or permanent repercussions as determined by other
|
66
|
+
members of the project's leadership.
|
67
|
+
|
68
|
+
## Attribution
|
69
|
+
|
70
|
+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
|
71
|
+
available at [http://contributor-covenant.org/version/1/4][version]
|
72
|
+
|
73
|
+
[homepage]: http://contributor-covenant.org
|
74
|
+
[version]: http://contributor-covenant.org/version/1/4/
|
data/Gemfile
ADDED
@@ -0,0 +1,25 @@
|
|
1
|
+
# frozen_string_literal: true
|
2
|
+
|
3
|
+
source 'https://rubygems.org'
|
4
|
+
|
5
|
+
# Specify your gem's dependencies in handlebars_helpers.gemspec
|
6
|
+
gemspec
|
7
|
+
|
8
|
+
# group :development do
|
9
|
+
# # Currently conflicts with GitHub actions and so I remove it on push
|
10
|
+
# # pry on steroids
|
11
|
+
# gem 'jazz_fingers'
|
12
|
+
# gem 'pry-coolline', github: 'owst/pry-coolline', branch: 'support_new_pry_config_api'
|
13
|
+
# end
|
14
|
+
|
15
|
+
group :development, :test do
|
16
|
+
gem 'guard-bundler'
|
17
|
+
gem 'guard-rspec'
|
18
|
+
gem 'guard-rubocop'
|
19
|
+
gem 'rake', '~> 12.0'
|
20
|
+
gem 'rake-compiler', require: false
|
21
|
+
gem 'rspec', '~> 3.0'
|
22
|
+
gem 'rubocop'
|
23
|
+
gem 'rubocop-rake', require: false
|
24
|
+
gem 'rubocop-rspec', require: false
|
25
|
+
end
|
data/Guardfile
ADDED
@@ -0,0 +1,30 @@
|
|
1
|
+
# frozen_string_literal: true
|
2
|
+
|
3
|
+
guard :bundler, cmd: 'bundle install' do
|
4
|
+
watch('Gemfile')
|
5
|
+
watch('k_fileset.gemspec')
|
6
|
+
end
|
7
|
+
|
8
|
+
group :green_pass_then_cop, halt_on_fail: true do
|
9
|
+
guard :rspec, cmd: 'bundle exec rspec -f doc' do
|
10
|
+
require 'guard/rspec/dsl'
|
11
|
+
dsl = Guard::RSpec::Dsl.new(self)
|
12
|
+
|
13
|
+
# RSpec files
|
14
|
+
rspec = dsl.rspec
|
15
|
+
watch(rspec.spec_helper) { rspec.spec_dir }
|
16
|
+
watch(rspec.spec_support) { rspec.spec_dir }
|
17
|
+
watch(rspec.spec_files)
|
18
|
+
|
19
|
+
# Ruby files
|
20
|
+
ruby = dsl.ruby
|
21
|
+
dsl.watch_spec_files_for(ruby.lib_files)
|
22
|
+
watch(%r{^lib/k_fileset/(.+)\.rb$}) { |m| "spec/unit/#{m[1]}_spec.rb" }
|
23
|
+
watch(%r{^lib/k_fileset/commands/(.+)\.rb$}) { |m| "spec/unit/commands/#{m[1]}_spec.rb" }
|
24
|
+
end
|
25
|
+
|
26
|
+
# guard :rubocop, all_on_start: false, cli: ['--format', 'clang'] do
|
27
|
+
# watch(/{.+\.rb$/)
|
28
|
+
# watch(%r{(?:.+/)?\.rubocop(?:_todo)?\.yml$}) { |m| File.dirname(m[0]) }
|
29
|
+
# end
|
30
|
+
end
|
data/LICENSE.txt
ADDED
@@ -0,0 +1,21 @@
|
|
1
|
+
The MIT License (MIT)
|
2
|
+
|
3
|
+
Copyright (c) 2022 David Cruwys
|
4
|
+
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
7
|
+
in the Software without restriction, including without limitation the rights
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
10
|
+
furnished to do so, subject to the following conditions:
|
11
|
+
|
12
|
+
The above copyright notice and this permission notice shall be included in
|
13
|
+
all copies or substantial portions of the Software.
|
14
|
+
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
|
21
|
+
THE SOFTWARE.
|
data/README.md
ADDED
@@ -0,0 +1,89 @@
|
|
1
|
+
# K Fileset
|
2
|
+
|
3
|
+
> K-Fileset provides file system snapshot using GLOB inclusions and exclusions
|
4
|
+
|
5
|
+
## Installation
|
6
|
+
|
7
|
+
Add this line to your application's Gemfile:
|
8
|
+
|
9
|
+
```ruby
|
10
|
+
gem 'k_fileset'
|
11
|
+
```
|
12
|
+
|
13
|
+
And then execute:
|
14
|
+
|
15
|
+
```bash
|
16
|
+
bundle install
|
17
|
+
```
|
18
|
+
|
19
|
+
Or install it yourself as:
|
20
|
+
|
21
|
+
```bash
|
22
|
+
gem install k_fileset
|
23
|
+
```
|
24
|
+
|
25
|
+
## Stories
|
26
|
+
|
27
|
+
### Main Story
|
28
|
+
|
29
|
+
As a Developer, I want a path/file snapshot files on a computer, so I can access and manipulate files matching my pattern
|
30
|
+
|
31
|
+
See all [stories](./STORIES.md)
|
32
|
+
|
33
|
+
## Usage
|
34
|
+
|
35
|
+
See all [usage examples](./USAGE.md)
|
36
|
+
|
37
|
+
### Basic Example
|
38
|
+
|
39
|
+
#### Basic example
|
40
|
+
|
41
|
+
Description for a basic example to be featured in the main README.MD file
|
42
|
+
|
43
|
+
```ruby
|
44
|
+
class SomeRuby; end
|
45
|
+
```
|
46
|
+
|
47
|
+
## Development
|
48
|
+
|
49
|
+
Checkout the repo
|
50
|
+
|
51
|
+
```bash
|
52
|
+
git clone klueless-io/k_fileset
|
53
|
+
```
|
54
|
+
|
55
|
+
After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests.
|
56
|
+
|
57
|
+
You can also run `bin/console` for an interactive prompt that will allow you to experiment.
|
58
|
+
|
59
|
+
```bash
|
60
|
+
bin/console
|
61
|
+
|
62
|
+
Aaa::Bbb::Program.execute()
|
63
|
+
# => ""
|
64
|
+
```
|
65
|
+
|
66
|
+
`k_fileset` is setup with Guard, run `guard`, this will watch development file changes and run tests automatically, if successful, it will then run rubocop for style quality.
|
67
|
+
|
68
|
+
To release a new version, update the version number in `version.rb`, build the gem and push the `.gem` file to [rubygems.org](https://rubygems.org).
|
69
|
+
|
70
|
+
```bash
|
71
|
+
rake publish
|
72
|
+
rake clean
|
73
|
+
```
|
74
|
+
|
75
|
+
## Contributing
|
76
|
+
|
77
|
+
Bug reports and pull requests are welcome on GitHub at https://github.com/klueless-io/k_fileset. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [Contributor Covenant](http://contributor-covenant.org) code of conduct.
|
78
|
+
|
79
|
+
## License
|
80
|
+
|
81
|
+
The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
|
82
|
+
|
83
|
+
## Code of Conduct
|
84
|
+
|
85
|
+
Everyone interacting in the K Fileset project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/klueless-io/k_fileset/blob/master/CODE_OF_CONDUCT.md).
|
86
|
+
|
87
|
+
## Copyright
|
88
|
+
|
89
|
+
Copyright (c) David Cruwys. See [MIT License](LICENSE.txt) for further details.
|
data/Rakefile
ADDED
@@ -0,0 +1,33 @@
|
|
1
|
+
# frozen_string_literal: true
|
2
|
+
|
3
|
+
# source: https://stephenagrice.medium.com/making-a-command-line-ruby-gem-write-build-and-push-aec24c6c49eb
|
4
|
+
|
5
|
+
GEM_NAME = 'k_fileset'
|
6
|
+
|
7
|
+
require 'bundler/gem_tasks'
|
8
|
+
require 'rspec/core/rake_task'
|
9
|
+
require 'k_fileset/version'
|
10
|
+
|
11
|
+
RSpec::Core::RakeTask.new(:spec)
|
12
|
+
|
13
|
+
require 'rake/extensiontask'
|
14
|
+
|
15
|
+
desc 'Compile all the extensions'
|
16
|
+
task build: :compile
|
17
|
+
|
18
|
+
Rake::ExtensionTask.new('k_fileset') do |ext|
|
19
|
+
ext.lib_dir = 'lib/k_fileset'
|
20
|
+
end
|
21
|
+
|
22
|
+
desc 'Publish the gem to RubyGems.org'
|
23
|
+
task :publish do
|
24
|
+
system 'gem build'
|
25
|
+
system "gem push #{GEM_NAME}-#{KFileset::VERSION}.gem"
|
26
|
+
end
|
27
|
+
|
28
|
+
desc 'Remove old *.gem files'
|
29
|
+
task :clean do
|
30
|
+
system 'rm *.gem'
|
31
|
+
end
|
32
|
+
|
33
|
+
task default: %i[clobber compile spec]
|
data/STORIES.md
ADDED
@@ -0,0 +1,52 @@
|
|
1
|
+
# K Fileset
|
2
|
+
|
3
|
+
> K-Fileset provides file system snapshot using GLOB inclusions and exclusions
|
4
|
+
|
5
|
+
As a Developer, I want a path/file snapshot files on a computer, so I can access and manipulate files matching my pattern
|
6
|
+
|
7
|
+
## Development radar
|
8
|
+
|
9
|
+
### Stories next on list
|
10
|
+
|
11
|
+
As a Developer, I want a path/file snapshot files on a computer, so I can access and manipulate files matching my pattern
|
12
|
+
|
13
|
+
- Create a file set
|
14
|
+
- Have a whitelist of included files
|
15
|
+
- Have regex or glob patterns for excluded files
|
16
|
+
|
17
|
+
### Tasks next on list
|
18
|
+
|
19
|
+
As a Developer, I want to add or remove files based on configured pattern (include/exclude) when files are added or removed from filesystem
|
20
|
+
|
21
|
+
- Be able to add or remove files from the fileset
|
22
|
+
|
23
|
+
Setup GitHub Action (test and lint)
|
24
|
+
|
25
|
+
- Setup Rspec action
|
26
|
+
- Setup RuboCop action
|
27
|
+
|
28
|
+
## Stories and tasks
|
29
|
+
|
30
|
+
### Tasks - completed
|
31
|
+
|
32
|
+
Setup RubyGems and RubyDoc
|
33
|
+
|
34
|
+
- Build and deploy gem to [rubygems.org](https://rubygems.org/gems/k_fileset)
|
35
|
+
- Attach documentation to [rubydoc.info](https://rubydoc.info/github/to-do-/k_fileset/master)
|
36
|
+
|
37
|
+
Setup project management, requirement and SCRUM documents
|
38
|
+
|
39
|
+
- Setup readme file
|
40
|
+
- Setup user stories and tasks
|
41
|
+
- Setup a project backlog
|
42
|
+
- Setup an examples/usage document
|
43
|
+
|
44
|
+
Setup new Ruby GEM
|
45
|
+
|
46
|
+
- Build out a standard GEM structure
|
47
|
+
- Add automated semantic versioning
|
48
|
+
- Add Rspec unit testing framework
|
49
|
+
- Add RuboCop linting
|
50
|
+
- Add Guard for automatic watch and test
|
51
|
+
- Add GitFlow support
|
52
|
+
- Add GitHub Repository
|
data/USAGE.md
ADDED
@@ -0,0 +1,19 @@
|
|
1
|
+
# K Fileset
|
2
|
+
|
3
|
+
> K-Fileset provides file system snapshot using GLOB inclusions and exclusions
|
4
|
+
|
5
|
+
As a Developer, I want a path/file snapshot files on a computer, so I can access and manipulate files matching my pattern
|
6
|
+
|
7
|
+
## Usage
|
8
|
+
|
9
|
+
### Sample Classes
|
10
|
+
|
11
|
+
#### Simple example
|
12
|
+
|
13
|
+
Description for a simple example that shows up in the USAGE.MD
|
14
|
+
|
15
|
+
```ruby
|
16
|
+
class SomeRuby
|
17
|
+
def initialize; end
|
18
|
+
end
|
19
|
+
```
|
data/bin/console
ADDED
@@ -0,0 +1,16 @@
|
|
1
|
+
#!/usr/bin/env ruby
|
2
|
+
|
3
|
+
# frozen_string_literal: true
|
4
|
+
|
5
|
+
require 'bundler/setup'
|
6
|
+
require 'k_fileset'
|
7
|
+
|
8
|
+
# You can add fixtures and/or initialization code here to make experimenting
|
9
|
+
# with your gem easier. You can also use a different console, if you like.
|
10
|
+
|
11
|
+
# (If you use this, don't forget to add pry to your Gemfile!)
|
12
|
+
# require 'pry'
|
13
|
+
# Pry.start
|
14
|
+
|
15
|
+
require 'irb'
|
16
|
+
IRB.start(__FILE__)
|
data/bin/k
ADDED
@@ -0,0 +1,36 @@
|
|
1
|
+
#!/usr/bin/env ruby
|
2
|
+
# frozen_string_literal: true
|
3
|
+
|
4
|
+
# NOTE: you may need change file permissions
|
5
|
+
# chmod +x bin/k
|
6
|
+
|
7
|
+
help = %(
|
8
|
+
----------------------------------------------------------------------
|
9
|
+
Klue Scripts - Help
|
10
|
+
----------------------------------------------------------------------
|
11
|
+
k - This Help File
|
12
|
+
|
13
|
+
khotfix - Create Hot Fix
|
14
|
+
Hot fixes are created in GIT and versioned correctly.
|
15
|
+
The patch # will increment by 1.
|
16
|
+
e.g. v0.1.1 will become v0.1.2
|
17
|
+
The version.rb file will also store the current version.
|
18
|
+
usage:
|
19
|
+
khotfix 'name of my cool hotfix'
|
20
|
+
|
21
|
+
kgitsync - Synchronize the master and development git repositories
|
22
|
+
Pulls latest code, pushes current changes
|
23
|
+
usage:
|
24
|
+
kgitsync
|
25
|
+
|
26
|
+
----------------------------------------------------------------------
|
27
|
+
Rake Tasks
|
28
|
+
----------------------------------------------------------------------
|
29
|
+
|
30
|
+
rails db:seed - load seed data
|
31
|
+
|
32
|
+
rails db:seed sample=true - load sample data, useful in developer environments
|
33
|
+
|
34
|
+
rails db:seed reset=true - reset database
|
35
|
+
)
|
36
|
+
puts help
|
data/bin/kgitsync
ADDED
@@ -0,0 +1,76 @@
|
|
1
|
+
#!/usr/bin/env bash
|
2
|
+
|
3
|
+
#NOTE: you may need change file permissions
|
4
|
+
# chmod +x bin/kgitsync
|
5
|
+
|
6
|
+
# Set up colour support, if we have it
|
7
|
+
# Are stdout and stderr both connected to a terminal
|
8
|
+
# If not then don't set colours
|
9
|
+
if [ -t 1 -a -t 2 ]
|
10
|
+
then
|
11
|
+
if tput -V >/dev/null 2>&1
|
12
|
+
then
|
13
|
+
C_RED=`tput setaf 1`
|
14
|
+
C_GREEN=`tput setaf 2`
|
15
|
+
C_BROWN=`tput setaf 3`
|
16
|
+
C_BLUE=`tput setaf 4`
|
17
|
+
C_RESET=`tput sgr0`
|
18
|
+
fi
|
19
|
+
fi
|
20
|
+
|
21
|
+
|
22
|
+
exit_error ()
|
23
|
+
{
|
24
|
+
# dont display if string is zero length
|
25
|
+
[ -z "$1" ] || echo "${C_RED}Error: ${C_BROWN} $1 ${C_RESET}"
|
26
|
+
exit 1
|
27
|
+
}
|
28
|
+
|
29
|
+
|
30
|
+
# make sure we are in a git tree
|
31
|
+
[ "`git rev-parse --is-inside-work-tree`" = "true" ] || exit_error "NOT a git repository"
|
32
|
+
echo "Repository check OK"
|
33
|
+
|
34
|
+
CURRENT_BRANCH=`git branch | awk '/^\*/{print $2}'`
|
35
|
+
|
36
|
+
# check that we are on develop or master
|
37
|
+
#[ "${CURRENT_BRANCH}" = "master" -o "${CURRENT_BRANCH}" = "develop" ] || exit_error "You MUST be on either the master or development branch"
|
38
|
+
#echo "Branch check OK"
|
39
|
+
|
40
|
+
# check that the current branch is clean
|
41
|
+
[ -z "`git status --porcelain`" ] || exit_error "Working copy has uncommitted changes"
|
42
|
+
echo "Working copy is clean OK"
|
43
|
+
|
44
|
+
# fetch from origin
|
45
|
+
git fetch origin || exit_error "Failed to fetch from origin"
|
46
|
+
|
47
|
+
######################
|
48
|
+
# Do develop
|
49
|
+
######################
|
50
|
+
git checkout develop || exit_error "Failed to checkout develop branch"
|
51
|
+
echo "Switched to develop"
|
52
|
+
git merge origin/develop || exit_error "Failed to merge develop from origin"
|
53
|
+
echo "Develop branch upto date"
|
54
|
+
git push || exit_error "Failed to push develop to origin"
|
55
|
+
echo "Develop pushed to origin"
|
56
|
+
|
57
|
+
######################
|
58
|
+
# Do master
|
59
|
+
######################
|
60
|
+
git checkout master || exit_error "Failed to checkout master branch"
|
61
|
+
echo "Switched to master"
|
62
|
+
git merge origin/master || exit_error "Failed to merge master from origin"
|
63
|
+
echo "Master branch upto date"
|
64
|
+
git push || exit_error "Failed to push master to origin"
|
65
|
+
echo "Master pushed to origin"
|
66
|
+
|
67
|
+
######################
|
68
|
+
# Do tags
|
69
|
+
######################
|
70
|
+
git push --tags || exit_error "Failed to push tags to origin"
|
71
|
+
echo "Tags pushed to origin"
|
72
|
+
|
73
|
+
# return to the current branch
|
74
|
+
git checkout ${CURRENT_BRANCH} || exit_error "Failed to return to your origional branch ${CURRENT_BRANCH}"
|
75
|
+
|
76
|
+
echo "${C_GREEN}Done. you are on ${CURRENT_BRANCH}${C_RESET}"
|