mutils 1.3.5 → 1.3.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,37 +0,0 @@
1
- ---
2
- name: Feature Request
3
- about: Suggest an idea for improvement
4
- title: "[FEATURE] Briefly describe the feature request"
5
- labels: enhancement
6
- assignees: ""
7
- ---
8
-
9
- ## Feature Request
10
-
11
- ### Description:
12
-
13
- [Provide a clear and concise description of the feature you're requesting.]
14
-
15
- ### Use Case:
16
-
17
- [Explain the use case or scenario where this feature would be beneficial.]
18
-
19
- ### Proposed Solution:
20
-
21
- [If you have a specific solution in mind, describe it here.]
22
-
23
- ### Alternatives Considered:
24
-
25
- [Have you considered any alternative solutions or workarounds?]
26
-
27
- ### Additional Context:
28
-
29
- [Add any additional context or information that might be relevant to the feature request.]
30
-
31
- ### Checklist:
32
-
33
- - [ ] I have searched for a similar feature request and didn't find any duplicates.
34
- - [ ] I have included all the required information.
35
- - [ ] I have tagged the issue with the label "enhancement."
36
-
37
- <!-- Feel free to add any other details that might help in understanding or implementing the requested feature. -->
@@ -1,25 +0,0 @@
1
- ---
2
- name: Question/Help
3
- about: Ask a question or seek help
4
- title: "[QUESTION] Briefly describe your question or issue"
5
- labels: question
6
- assignees: ""
7
- ---
8
-
9
- ## Question/Help
10
-
11
- ### Description:
12
-
13
- [Briefly describe the question or issue you need help with.]
14
-
15
- ### Context:
16
-
17
- [Provide any relevant context or details that might help others understand your question or issue better.]
18
-
19
- ### Checklist:
20
-
21
- - [ ] I have searched for similar questions or issues and found none.
22
- - [ ] I have included all the required information.
23
- - [ ] I have tagged the issue with the label "question."
24
-
25
- <!-- Feel free to add any additional details that might help in addressing your question or issue. -->
@@ -1,74 +0,0 @@
1
- ---
2
- name: Report a security vulnerability
3
- about: Report a security vulnerability to help us improve
4
- title: "[SECURITY] Write a concise title here"
5
- labels: security
6
- assignees: ""
7
- ---
8
-
9
- <!-- If you believe you have found a security vulnerability in our project, please follow these steps to report it to us. We appreciate your efforts in disclosing the issue responsibly and will work with you to address the problem promptly. -->
10
-
11
- # Security Vulnerability Report
12
-
13
- ## Title:
14
-
15
- [Concise title describing the vulnerability]
16
-
17
- ## Contact Information:
18
-
19
- [Your contact information - email or other preferred means of contact]
20
- [Remember that this information may be publicly visible depending on the project's settings]
21
-
22
- ## Description:
23
-
24
- [Detailed description of the vulnerability, including steps to reproduce if possible]
25
-
26
- ## Supporting Documentation:
27
-
28
- [Attach any supporting documentation, code, or relevant information]
29
-
30
- ## Impact:
31
-
32
- [Describe the impact of the vulnerability]
33
-
34
- ## Suggestions to Fix:
35
-
36
- [If you have suggestions on how to fix the vulnerability, please include them here]
37
-
38
- ## Steps to uncover:
39
-
40
- [If you have suggestions on how to uncover the vulnerability, please include them here]
41
-
42
- ## Steps to reproduce:
43
-
44
- [If you have suggestions on how to reproduce the vulnerability, please include them here]
45
-
46
- ## Severity:
47
-
48
- [Low/Medium/High]
49
-
50
- ## Affected Versions:
51
-
52
- [List affected versions here]
53
-
54
- ## Checklist:
55
-
56
- - [ ] I have filled out all the fields above
57
- - [ ] I have searched for a similar issue in the project and found none
58
- - [ ] I have tagged the issue with the label "security"
59
- - [ ] I understand that I may be contacted for further information and my contact information lies in the issue which may be publicly visible depending on the project's settings
60
- - [ ] I understand and agree to license the code I am providing under the project's license
61
-
62
- <!--
63
- After creating the issue, tag it with the label "security". This will notify the project maintainers and we will respond as soon as possible.
64
-
65
- Our Response: We will acknowledge your report as soon as possible and provide an estimated timeline for when you can expect a resolution.
66
-
67
- Coordination: We will work with you to address the issue, and if necessary, coordinate the release of a fix.
68
-
69
- Bounty: We do not offer a bounty for the disclosure of security vulnerabilities for public projects, but we will publicly thank you for your assistance unless you request to remain anonymous. If the project is private, we may offer a bounty at our discretion.
70
-
71
- Code and License: The effective license for the code in the project is applied to the code provided by you in the report. If you provide a patch, you agree to license the code under the project's license.
72
-
73
- Legal Safe Harbor: We will not take legal action against you or suspend your account if you follow the responsible disclosure process. We appreciate your assistance in helping us maintain the security of our project.
74
- -->
@@ -1,51 +0,0 @@
1
- ---
2
- name: Translation Issue Report
3
- about: Create a report to help us improve translations
4
- title: "[TRANSLATION] Briefly describe the issue"
5
- labels: translation
6
- assignees: ""
7
- ---
8
-
9
- # Translation Issue Report
10
-
11
- ## Description:
12
-
13
- [Provide a clear and concise description of the translation issue.]
14
-
15
- ## Context:
16
-
17
- [Explain the context in which the translation issue occurred.]
18
-
19
- ## Source Language:
20
-
21
- [Specify the language of the original content.]
22
-
23
- ## Target Language:
24
-
25
- [Specify the language the content was translated into.]
26
-
27
- ## Incorrect Translation:
28
-
29
- [Provide the section or phrase that is incorrectly translated.]
30
-
31
- ## Suggested Translation:
32
-
33
- [Offer your suggested correction or improvement.]
34
-
35
- ## Screenshots or Additional Information:
36
-
37
- [If applicable, add screenshots or other information to help illustrate the translation issue.]
38
-
39
- ## Environment:
40
-
41
- - Operating System: [e.g., Windows, macOS, Linux]
42
- - Browser (if applicable): [e.g., Chrome, Firefox, Safari]
43
- - Version: [e.g., 1.0.0]
44
-
45
- ## Checklist:
46
-
47
- - [ ] I have searched for similar translation issues and didn't find any duplicates.
48
- - [ ] I have included all the relevant information.
49
- - [ ] I have tagged the issue with the label "translation."
50
-
51
- <!-- Feel free to add any additional details or context that might be helpful in addressing the translation issue. -->
@@ -1,52 +0,0 @@
1
- <!--
2
- The title of the GitHub must follow the following format:
3
- [BUG/DOCS/FEATURE/SECURITY/TRANSLATION] Briefly describe the changes made in this pull request.
4
-
5
- If your pull request doesn't fall under any of the above categories, please use the label "OTHER" and describe the changes in the title.
6
-
7
- For example:
8
- [FEATURE] Add a new feature to the project
9
- [BUG] Fix bug in the project
10
- [DOCS] Update documentation
11
- [SECURITY] Fix security vulnerability
12
- [TRANSLATION] Translate content into a new language
13
- [OTHER] Briefly describe the changes made in this pull request
14
-
15
- A CLA is required for this pull request. Please read and sign the CLA at https://cla.developers.codevedas.com
16
- -->
17
-
18
- ## Pull Request
19
-
20
- ### Description:
21
-
22
- [Provide a clear and concise description of the changes introduced by this pull request.]
23
-
24
- ### Related Issue:
25
-
26
- [If your pull request addresses a specific issue, reference it here by linking to the issue using the pound sign (#). For example, #123]
27
-
28
- ### Proposed Changes:
29
-
30
- [Outline the changes made in this pull request. Include any new features, bug fixes, or enhancements.]
31
-
32
- ### Checklist:
33
-
34
- - [ ] I have tested these changes locally.
35
- - [ ] I have ensured that my code follows the project's coding standards.
36
- - [ ] I have updated the documentation (if applicable).
37
- - [ ] I have added appropriate tests (if applicable).
38
- - [ ] I have updated relevant comments in the code (if applicable).
39
- - [ ] I have confirmed that the changes work with the latest version of dependencies.
40
- - [ ] I have added appropriate labels to the pull request.
41
-
42
- ### Screenshots or Additional Information:
43
-
44
- [If applicable, provide screenshots or any additional information that helps reviewers understand the changes.]
45
-
46
- ### Environment:
47
-
48
- - Operating System: [e.g., Windows, macOS, Linux]
49
- - Browser (if applicable): [e.g., Chrome, Firefox, Safari]
50
- - Version: [e.g., 1.0.0]
51
-
52
- <!-- Feel free to add any additional details or context that might be helpful in reviewing the pull request. -->
@@ -1,11 +0,0 @@
1
- version: 2
2
- updates:
3
- - package-ecosystem: "bundler"
4
- directory: "/"
5
- schedule:
6
- interval: "daily"
7
- - package-ecosystem: github-actions
8
- directory: "/"
9
- schedule:
10
- interval: daily
11
- open-pull-requests-limit: 10
@@ -1,148 +0,0 @@
1
- name-template: "v$RESOLVED_VERSION"
2
- tag-template: "v$RESOLVED_VERSION"
3
-
4
- autolabeler:
5
- - label: "dependencies"
6
- branch:
7
- - /^dependabot\//
8
- title:
9
- - /^chore\(deps\):/
10
- - /^chore\(dependencies\):/
11
- - label: "feature"
12
- branch:
13
- - /^feat\//
14
- title:
15
- - /^feat:/
16
-
17
- - label: "bug"
18
- branch:
19
- - /^bugfix\//
20
- title:
21
- - /^bugfix:/
22
-
23
- - label: "docs"
24
- branch:
25
- - /^docs\//
26
- title:
27
- - /^docs:/
28
-
29
- - label: "release"
30
- branch:
31
- - /^release\//
32
- title:
33
- - /^release:/
34
-
35
- - label: "chore"
36
- branch:
37
- - /^chore\//
38
- title:
39
- - /^chore:/
40
-
41
- - label: "refactor"
42
- branch:
43
- - /^refactor\//
44
- title:
45
- - /^refactor:/
46
-
47
- - label: "test"
48
- branch:
49
- - /^test\//
50
- title:
51
- - /^test:/
52
-
53
- - label: "style"
54
- branch:
55
- - /^style\//
56
- title:
57
- - /^style:/
58
-
59
- - label: "ci"
60
- branch:
61
- - /^ci\//
62
- title:
63
- - /^ci:/
64
-
65
- - label: "perf"
66
- branch:
67
- - /^perf\//
68
- title:
69
- - /^perf:/
70
-
71
- - label: "build"
72
- branch:
73
- - /^build\//
74
- title:
75
- - /^build:/
76
-
77
- categories:
78
- - title: "🚀 Features"
79
- labels:
80
- - "feature"
81
-
82
- - title: "🐛 Bug Fixes"
83
- labels:
84
- - "bug"
85
-
86
- - title: "📝 Documentation"
87
- labels:
88
- - "docs"
89
-
90
- - title: "🔖 Releases"
91
- labels:
92
- - "release"
93
-
94
- - title: "🧰 Maintenance"
95
- labels:
96
- - "chore"
97
- - "refactor"
98
- - "dependencies"
99
-
100
- - title: "🧪 Tests"
101
- labels:
102
- - "test"
103
-
104
- - title: "💅 Styling"
105
- labels:
106
- - "style"
107
-
108
- - title: "⚙️ CI"
109
- labels:
110
- - "ci"
111
-
112
- - title: "🚀 Performance"
113
- labels:
114
- - "perf"
115
-
116
- - title: "📦 Build"
117
- labels:
118
- - "build"
119
-
120
- change-template: "- $TITLE @$AUTHOR (#$NUMBER)"
121
- no-changes-template: "- No user-facing changes."
122
-
123
- version-resolver:
124
- major:
125
- labels:
126
- - "breaking"
127
- minor:
128
- labels:
129
- - "feature"
130
- patch:
131
- labels:
132
- - "bug"
133
- - "chore"
134
- - "refactor"
135
- - "test"
136
- - "style"
137
- - "ci"
138
- - "perf"
139
- - "build"
140
- - "dependencies"
141
-
142
- exclude-labels:
143
- - "skip-changelog"
144
-
145
- template: |
146
- ## Changes
147
-
148
- $CHANGES
@@ -1,45 +0,0 @@
1
- name: Pull Requests
2
- on:
3
- push:
4
- branches: [main]
5
- pull_request:
6
- branches: [main]
7
- jobs:
8
- lint:
9
- runs-on: ubuntu-latest
10
- steps:
11
- - name: Checkout code
12
- uses: actions/checkout@v6
13
-
14
- - name: Set up Ruby
15
- uses: ruby/setup-ruby@v1
16
- with:
17
- ruby-version: 3.4.3
18
- bundler-cache: true
19
-
20
- - name: Lint code for consistent style
21
- run: bin/rubocop -f github
22
- test:
23
- runs-on: ubuntu-latest
24
- steps:
25
- - name: Install packages
26
- run: sudo apt-get update && sudo apt-get install --no-install-recommends -y build-essential git libyaml-dev pkg-config
27
-
28
- - name: Checkout code
29
- uses: actions/checkout@v6
30
-
31
- - name: Set up Ruby
32
- uses: ruby/setup-ruby@v1
33
- with:
34
- ruby-version: 3.4.3
35
- bundler-cache: true
36
-
37
- - name: Run tests
38
- run: bin/rspec --format documentation --color --profile
39
-
40
- - name: Upload simplecov report
41
- uses: actions/upload-artifact@v6
42
- with:
43
- name: simplecov-report
44
- path: ${{ github.workspace }}/coverage
45
- if-no-files-found: ignore
@@ -1,64 +0,0 @@
1
- name: "CodeQL"
2
-
3
- on:
4
- push:
5
- branches: ["*"]
6
- pull_request:
7
- # The branches below must be a subset of the branches above
8
- branches: ["*"]
9
- schedule:
10
- - cron: "26 6 * * 5"
11
-
12
- jobs:
13
- analyze:
14
- name: Analyze
15
- runs-on: ubuntu-latest
16
- permissions:
17
- actions: read
18
- contents: read
19
- security-events: write
20
-
21
- strategy:
22
- fail-fast: false
23
- matrix:
24
- language: ["ruby"]
25
- # CodeQL supports [ 'cpp', 'csharp', 'go', 'java', 'javascript', 'python', 'ruby' ]
26
- # Use only 'java' to analyze code written in Java, Kotlin or both
27
- # Use only 'javascript' to analyze code written in JavaScript, TypeScript or both
28
- # Learn more about CodeQL language support at https://aka.ms/codeql-docs/language-support
29
-
30
- steps:
31
- - name: Checkout repository
32
- uses: actions/checkout@v6
33
-
34
- # Initializes the CodeQL tools for scanning.
35
- - name: Initialize CodeQL
36
- uses: github/codeql-action/init@v4
37
- with:
38
- languages: ${{ matrix.language }}
39
- # If you wish to specify custom queries, you can do so here or in a config file.
40
- # By default, queries listed here will override any specified in a config file.
41
- # Prefix the list here with "+" to use these queries and those in the config file.
42
-
43
- # Details on CodeQL's query packs refer to : https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs
44
- # queries: security-extended,security-and-quality
45
-
46
- # Autobuild attempts to build any compiled languages (C/C++, C#, Go, or Java).
47
- # If this step fails, then you should remove it and run the build manually (see below)
48
- - name: Autobuild
49
- uses: github/codeql-action/autobuild@v4
50
-
51
- # ℹ️ Command-line programs to run using the OS shell.
52
- # 📚 See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun
53
-
54
- # If the Autobuild fails above, remove it and uncomment the following three lines.
55
- # modify them (or add more) to build your code if your project, please refer to the EXAMPLE below for guidance.
56
-
57
- # - run: |
58
- # echo "Run, Build Application using script"
59
- # ./location_of_script_within_repo/buildscript.sh
60
-
61
- - name: Perform CodeQL Analysis
62
- uses: github/codeql-action/analyze@v4
63
- with:
64
- category: "/language:${{matrix.language}}"
@@ -1,27 +0,0 @@
1
- name: Release Drafter
2
-
3
- on:
4
- push:
5
- branches:
6
- - main
7
- pull_request:
8
- types: [opened, reopened, synchronize]
9
-
10
- permissions:
11
- contents: write
12
- pull-requests: read
13
-
14
- jobs:
15
- release_drafter:
16
- permissions:
17
- contents: write
18
- pull-requests: write
19
- runs-on: ubuntu-latest
20
- steps:
21
- - uses: release-drafter/release-drafter@v6
22
- with:
23
- config-name: release-drafter.yml
24
- disable-releaser: ${{ github.event_name != 'push' }}
25
- disable-autolabeler: ${{ github.event_name != 'pull_request' }}
26
- env:
27
- GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
@@ -1,43 +0,0 @@
1
- name: Release
2
-
3
- on:
4
- push:
5
- tags:
6
- - "v*"
7
-
8
- jobs:
9
- test:
10
- name: Run RSpec
11
- runs-on: ubuntu-latest
12
- steps:
13
- - name: Checkout
14
- uses: actions/checkout@v6
15
- - name: Set up Ruby
16
- uses: ruby/setup-ruby@v1
17
- with:
18
- bundler-cache: true
19
- - name: RSpec
20
- run: bin/rspec
21
-
22
- push:
23
- runs-on: ubuntu-latest
24
- needs: test
25
- permissions:
26
- contents: write
27
- id-token: write
28
- environment: release
29
- steps:
30
- - uses: actions/checkout@v6
31
- with:
32
- persist-credentials: false
33
- - name: Set up Ruby
34
- uses: ruby/setup-ruby@v1
35
- with:
36
- bundler-cache: true
37
- ruby-version: ruby
38
- - name: Configure RubyGems Credentials
39
- uses: rubygems/configure-rubygems-credentials@main
40
- - name: Release
41
- run: |
42
- gem build mutils.gemspec
43
- gem push mutils-*.gem
data/.gitignore DELETED
@@ -1,15 +0,0 @@
1
- /.bundle/
2
- /.yardoc
3
- /_yardoc/
4
- /coverage/
5
- /doc/
6
- /pkg/
7
- /spec/reports/
8
- /tmp/
9
-
10
- # rspec failure tracking
11
- .rspec_status
12
- .idea/*
13
- *.gem
14
- /node_modules
15
- .DS_Store
data/.jrubyrc DELETED
@@ -1 +0,0 @@
1
- debug.fullTrace=true
data/.releaserc DELETED
@@ -1,64 +0,0 @@
1
- branch: master
2
- ci: false
3
- verifyConditions:
4
- - "@semantic-release/changelog"
5
- - "@semantic-release/git"
6
- - "@semantic-release/github"
7
- analyzeCommits:
8
- - "@semantic-release/commit-analyzer"
9
- generateNotes:
10
- path: "@semantic-release/release-notes-generator"
11
- preset: angular
12
- parserOpts:
13
- noteKeywords:
14
- - BREAKING CHANGE
15
- - BREAKING CHANGES
16
- - BREAKING
17
- writerOpts:
18
- commitsSort:
19
- - scope
20
- - subject
21
- presetConfig:
22
- types:
23
- - type: chore
24
- section: Chores
25
- - type: build
26
- section: Build Changes
27
- - type: docs
28
- section: Documentation Changes
29
- - type: feat
30
- section: Features
31
- - type: fix
32
- section: Bug Fixes
33
- - type: perf
34
- section: Performance Improvements
35
- - type: refactor
36
- section: Refactors
37
- - type: revert
38
- section: Reverted
39
- - type: style
40
- section: Styles Changes
41
- - type: test
42
- section: Test Suite Changes
43
- prepare:
44
- - path: "@semantic-release/changelog"
45
- changelogFile: CHANGELOG.md
46
- - path: "@semantic-release/exec"
47
- cmd: echo "v${nextRelease.version}" > Version
48
- - path: "@semantic-release/exec"
49
- cmd: 'bundle config unset deployment'
50
- - path: "@semantic-release/exec"
51
- cmd: 'bundle install'
52
- - path: "@semantic-release/exec"
53
- cmd: 'echo "Creating Version: $(cat Version)"'
54
- - path: "@semantic-release/git"
55
- assets:
56
- - CHANGELOG.md
57
- - Version
58
- - Gemfile.lock
59
- message: |-
60
- build(release): v${nextRelease.version} [skip ci]
61
-
62
- ${nextRelease.notes}
63
- publish:
64
- - "@semantic-release/github"
data/.rspec DELETED
@@ -1,2 +0,0 @@
1
- --color
2
- --require spec_helper
data/.rubocop.yml DELETED
@@ -1,13 +0,0 @@
1
- plugins:
2
- - rubocop-rake
3
- - rubocop-rspec
4
- AllCops:
5
- NewCops: enable
6
- TargetRubyVersion: 3.2
7
- SuggestExtensions: true
8
- Metrics/MethodLength:
9
- Max: 20
10
- RSpec/MultipleExpectations:
11
- Max: 10
12
- RSpec/ExampleLength:
13
- Max: 15
data/.ruby-version DELETED
@@ -1 +0,0 @@
1
- 3.4.3