slack_messaging 1.2.1 → 2.1.0

data/.github/issue_template.md

@@ -1,97 +0,0 @@
-Please fill in the section that best describes your Issue and delete all other sections.
-
-<details><summary>Bug Report</summary>
-
-  ## Bug Description
-
-  > A clear and concise description of what the bug is.
-
-  ## To Reproduce
-
-  > Steps to reproduce the behavior:
-
-  1. Go to "..."
-  2. Click on "..."
-  3. Scroll down to "..."
-  4. See error
-
-  ## Expected Behavior
-
-  > A clear and concise description of what you expected to happen.
-
-  ## Screenshots
-
-  > If applicable, add screenshots to help explain your problem.
-
-  ## Desktop
-
-  > Please complete the following information:
-
-  - OS: [e.g. iOS]
-  - Browser: [e.g. chrome, safari]
-  - Version: [e.g. 22]
-
-  ## Smartphone
-
-  > Please complete the following information:
-
-  - Device: [e.g. iPhone6]
-  - OS: [e.g. iOS8.1]
-  - Browser: [e.g. stock browser, safari]
-  - Version: [e.g. 22]
-
-  ## Additional Context
-
-  > Add any other context about the problem here.
-
-</details>
-
-<details><summary>Feature Request</summary>
-
-  ## Is this feature request related to a problem?
-
-  > A clear and concise description of what the problem is. Ex: I'm always frustrated when [...]
-
-  ## The Solution I'd Prefer
-
-  > A clear and concise description of what you want to happen.
-
-  ## Alternative Solutions I've Considered
-
-  > A clear and concise description of any alternative solutions or features you've considered.
-
-  ## Additional Context
-
-  > Add any other context or screenshots about the feature request here.
-
-</details>
-
-<details><summary>Security Report</summary>
-
-  ## What is the alert or vulnerability?
-
-  > A clear and concise description of what the vulnerability is. Ex: The Ruby gem [...] has reported vulnerability CVE-[...].
-
-  ## Where did you find out about this vulnerability?
-
-  > A clear and concise description of where this vulnerability was first reported or where you heard about it.
-
-  ## What are the risks of doing nothing?
-
-  > A clear and concise description of what will happen if we leave the vulnerability as is.
-
-  ## Suggestions for improvement?
-
-  > A clear and concise description of what can be done to mitigate this vulnerability.
-
-  ## Additional Context
-
-  > Add any other context, URLs, or screenshots about the alert or vulnerability.
-
-</details>
-
-<details><summary>General Question or Concern</summary>
-
-  ## What's your question or comment? Please add as much context as possible.
-
-</details>

data/.github/pull_request_template.md

@@ -1,19 +0,0 @@
-## Changes
-
-> A list of the changes that your PR will make:
-
-* Adding a page "..."
-* Refactoring "..."
-
-## Related PRs and Issues
-
-> If applicable, a list of related PRs and Issues:
-
-* Issue #1
-* Issue #2
-* Pull Request #1
-* Pull Request #2
-
-## Additional Context
-
-> Add any other context about the problem here.

data/.github/security.md

@@ -1,11 +0,0 @@
-# Security Policy
-
-## Reporting a Vulnerability
-
-If you happen to find any security vulnerabilities in this project, please let me know! I've turned on GitHub's security advisory and alert suggestions, but it's always possible that I'll miss something.
-
-To let me know there's a security vulnerability, please make a [new GitHub Issue](https://github.com/emmasax4/slack_messaging/issues/new) and fill in the Security Report section to the best of your capabilities.
-
-I'll respond on the Issue or take appropriate action as soon as I'm able.
-
-Thank you for helping my project to be as secure as possible.

data/.github/workflows/develop.yml

@@ -1,30 +0,0 @@
-name: Develop
-on:
-  push:
-    branches: [ main ]
-  pull_request:
-    branches: [ main ]
-
-jobs:
-  test:
-    runs-on: ubuntu-latest
-    steps:
-    - name: Check Out Code
-      uses: actions/checkout@v2
-      with:
-        fetch-depth: 0
-
-    - name: Define Run Variables
-      run: echo "::set-env name=BRANCH::$(echo ${{ github.head_ref }} | sed -E 's|refs/[a-zA-Z]+/||')"
-
-    - name: Switch to Current Branch
-      run: git checkout ${{ env.BRANCH }}
-
-    - name: Configure System
-      run: sudo gem update --system 3.0.8 && sudo gem install bundler
-
-    - name: Install Gems
-      run: bundle config set path "vendor/bundle" && bundle install
-
-    - name: Run Rspec Tests
-      run: bundle exec rspec

data/.gitignore

@@ -1,18 +0,0 @@
-/.bundle/
-/.yardoc
-/Gemfile.lock
-/_yardoc/
-/coverage/
-/doc/
-/pkg/
-/spec/reports/
-/tmp/
-*.bundle
-*.so
-*.o
-*.a
-mkmf.log
-
-.DS_Store
-*.gem
-.idea

data/.octopolo.yml

@@ -1,4 +0,0 @@
-github_repo: emmasax4/slack_messaging
-semantic_versioning: true
-branches_to_keep:
-- main

data/.rspec

@@ -1,2 +0,0 @@
---color
---require spec_helper

data/.ruby-gemset

@@ -1 +0,0 @@
-slack_messaging

data/.ruby-version

@@ -1 +0,0 @@
-ruby-2.7.1

data/.soyuz.yml

@@ -1,12 +0,0 @@
-defaults:
-  deploy_cmd: gem push *.gem
-  before_deploy_cmds:
-    - sed -i "" -e "s/\".*/\"$(git tag| sed s/v// | sort -n -t. -k1,1 -k2,2 -k3,3 | tail -1)\"/" lib/slack_messaging/version.rb
-    - git add  lib/slack_messaging/version.rb
-    - git commit -m "Version Bump" && git push
-    - gem build slack_messaging.gemspec
-  after_deploy_cmds:
-    - rm *.gem
-environments:
-  -
-    rubygems: {}

data/CHANGELOG.markdown

@@ -1,11 +0,0 @@
-#### v1.2.0
-* Update the gemspec to not have security vulnerabilities
-
-#### v1.1.0
-* Updating config.rb with more up to date information
-
-#### v1.0.1
-* Adding back in Changelog
-
-#### v1.0.0
-* Initial release

data/CODE_OF_CONDUCT.md

@@ -1,76 +0,0 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, sex characteristics, gender identity and expression,
-level of experience, education, socio-economic status, nationality, personal
-appearance, race, religion, or sexual identity and orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or
- advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
- address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
- professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers 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, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at emma.sax4@gmail.com. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
-
-[homepage]: https://www.contributor-covenant.org
-
-For answers to common questions about this code of conduct, see
-https://www.contributor-covenant.org/faq

data/CONTRIBUTING.md

@@ -1,11 +0,0 @@
-# Contributing
-
-1. Fork it (https://github.com/emmasax4/slack_messaging/fork)
-2. Create your feature branch (`git checkout -b my-new-feature`)
-3. Commit your changes (`git commit -am 'Add some feature'`)
-4. Push to the branch (`git push origin my-new-feature`)
-5. Continue making awesome changes!
-6. To see how it works, follow the [Usage section in the README.md](https://github.com/emmasax4/slack_messaging#usage)
-7. When you're satisfied, make a pull request to this repository
-8. If I don't comment or start looking at the pull request in a couple of days, feel free to send me [an email](mailto:emma.sax4@gmail.com)
-9. I approve your pull request and merge!

data/lib/slack_messaging/commands/slack.rb

@@ -1,7 +0,0 @@
-desc 'Prints a variety of messages to Slack'
-command 'slack' do |c|
-  c.action do |global_options, options, args|
-    require_relative '../scripts/slack'
-    SlackMessaging::Scripts::Slack.execute(args, options) # args are optional string to print
-  end
-end

data/lib/slack_messaging/output.rb

@@ -1,13 +0,0 @@
-require 'highline'
-
-module SlackMessaging
-  module Output
-    def self.terminal
-      @terminal ||= HighLine.new
-    end
-
-    def self.ask(*args, &block)
-      terminal.ask(*args, &block)
-    end
-  end
-end

data/lib/slack_messaging/scripts/slack.rb

@@ -1,29 +0,0 @@
-require 'highline/import'
-require_relative "../notify_slack"
-require_relative "../random_message"
-
-module SlackMessaging
-  module Scripts
-    class Slack
-      class << self
-        attr_accessor :options
-      end
-
-      def self.execute(args, options=nil)
-        if args.empty?
-          message = RandomMessage.new # generate a new random message
-          print_message(message.get_text)
-        else
-          args.each do |message|
-            print_message(message)
-          end
-        end
-      end
-
-      def self.print_message(message)
-        slack_job = NotifySlack.new(message)
-        slack_job.perform
-      end
-    end
-  end
-end

data/slack_messaging.gemspec

@@ -1,32 +0,0 @@
-# coding: utf-8
-lib = File.expand_path('../lib', __FILE__)
-$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
-require 'slack_messaging/version'
-
-Gem::Specification.new do |spec|
-  spec.name          = "slack_messaging"
-  spec.version       = SlackMessaging::VERSION
-  spec.authors       = ["Emma Sax"]
-  spec.email         = ["emma.sax4@gmail.com"]
-  spec.summary       = %q{Sending Personalized Slack Messages}
-  spec.description   = %q{Sending Personalized Slack Messages}
-  spec.homepage      = "https://github.com/emmasax4/slack_messaging"
-  spec.license       = "MIT"
-
-  spec.files         = `git ls-files -z`.split("\x0")
-  spec.executables   = spec.files.grep(%r{^bin/}) { |f| File.basename(f) }
-  spec.test_files    = spec.files.grep(%r{^(test|spec|features)/})
-  spec.require_paths = ["lib"]
-
-  spec.add_dependency 'hashie', '~> 3.3'
-  spec.add_dependency 'gli', '~> 2.10'
-  spec.add_dependency 'highline', '~> 1.6'
-  spec.add_dependency 'slack-notifier', '~> 1.5.1'
-  spec.add_dependency 'rack', '>= 2.1.4'
-  spec.add_dependency 'activesupport', '~> 4.1.11'
-
-  spec.add_development_dependency "bundler", "~> 2.1"
-  spec.add_development_dependency "rake", "~> 12.3.3"
-  spec.add_development_dependency "rspec", "~> 3.4.0"
-  spec.add_development_dependency 'simplecov'
-end