Skip to content

Commit 3ca52a7

Browse files
jhart1685jhart1685
authored
Merge pull request #1 from IBM/initialCommit
Initial check-in of generated code and associated tests
2 parents 3d4da6b + 8e83553 commit 3ca52a7

36 files changed

+13719
-2
lines changed

‎.bumpversion.cfg

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
[bumpversion]
2+
current_version = 0.0.1
3+
commit = True
4+
message = Update version {current_version} -> {new_version}
5+
6+
[bumpversion:file:ibm_container_registry/version.py]
7+
search = __version__ = '{current_version}'
8+
replace = __version__ = '{new_version}'
9+
10+
[bumpversion:file:setup.py]
11+
search = __version__ = '{current_version}'
12+
replace = __version__ = '{new_version}'
13+
14+
[bumpversion:file:README.md]
15+
search = {current_version}
16+
replace = {new_version}
17+

‎.gitattributes

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
*.enc binary

‎.github/ISSUE_TEMPLATE/bug_report.md

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
---
2+
name: Bug report
3+
about: Create a bug report to help us improve
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
**Describe the bug**
11+
A clear and concise description of what the bug is.
12+
13+
**To Reproduce**
14+
List the steps that can be used to demonstrate the bug. Include the name of the service and operation that you're trying to invoke, if applicable. Be sure to describe any relevant info regarding parameter values used with your API invocation.
15+
16+
**Expected behavior**
17+
A clear and concise description of what you expected to happen.
18+
19+
**Screenshots**
20+
If applicable, add screenshots to help explain your problem.
21+
22+
**Must gather (please complete the following information):**
23+
- SDK Version [e.g. 1.2.1]
24+
- Python Version [e.g. 3.5]
25+
- Name of service that you're trying to use (if applicable)
26+
- Name of operation that you're trying to invoke (if applicable)
27+
28+
**Additional context**
29+
Add any other context about the problem here.
30+
Were you able to avoid the problem by changing your application code slightly?

‎.github/ISSUE_TEMPLATE/feature_request.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
**Is your feature request related to a problem? Please describe.**
11+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12+
13+
**Describe the solution you'd like**
14+
A clear and concise description of what you want to happen.
15+
16+
**Describe alternatives you've considered**
17+
A clear and concise description of any alternative solutions or features you've considered.
18+
19+
**Additional context**
20+
Add any other context or screenshots about the feature request here.

‎.github/pull_request_template.md

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
## PR summary
2+
<!-- please include a brief summary of the changes in this PR -->
3+
4+
**Fixes:** <! -- link to issue -->
5+
6+
## PR Checklist
7+
Please make sure that your PR fulfills the following requirements:
8+
- [ ] The commit message follows the [Angular Commit Message Guidelines](https://github.com/angular/angular/blob/master/CONTRIBUTING.md#-commit-message-guidelines).
9+
- [ ] Tests for the changes have been added (for bug fixes / features)
10+
- [ ] Docs have been added / updated (for bug fixes / features)
11+
12+
## PR Type
13+
<!-- Please check the one that applies to this PR using "x". -->
14+
- [ ] Bugfix
15+
- [ ] Feature
16+
- [ ] Code style update (formatting, local variables)
17+
- [ ] Refactoring (no functional changes, no api changes)
18+
- [ ] New tests
19+
- [ ] Build/CI related changes
20+
- [ ] Documentation content changes
21+
- [ ] Other (please describe)
22+
23+
## What is the current behavior?
24+
<!-- Please describe the current behavior that you are modifying. -->
25+
26+
## What is the new behavior?
27+
<!-- Please describe the new behavior after your change. -->
28+
29+
## Does this PR introduce a breaking change?
30+
- [ ] Yes
31+
- [ ] No
32+
33+
<!-- If this PR contains a breaking change, please describe the impact and migration path for existing applications below. -->
34+
35+
## Other information
36+
<!-- Please add any additional information that would help reviewers evaluate your PR -->

‎.gitignore

Lines changed: 75 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,75 @@
1+
# IDE OS
2+
.DS_Store
3+
.idea
4+
.project
5+
6+
# Byte-compiled / optimized / DLL files
7+
__pycache__/
8+
*.py[cod]
9+
*$py.class
10+
11+
# Distribution / packaging
12+
.Python
13+
env/
14+
build/
15+
develop-eggs/
16+
dist/
17+
eggs/
18+
.eggs/
19+
lib/
20+
lib64/
21+
parts/
22+
sdist/
23+
var/
24+
*.egg-info/
25+
.installed.cfg
26+
*.egg
27+
28+
# PyInstaller
29+
# Usually these files are written by a python script from a template
30+
# before PyInstaller builds the exe, so as to inject date/other infos into it.
31+
*.manifest
32+
*.spec
33+
34+
# Installer logs
35+
pip-log.txt
36+
pip-delete-this-directory.txt
37+
38+
# Unit test / coverage reports
39+
htmlcov/
40+
.tox/
41+
.coverage
42+
.coverage.*
43+
.cache
44+
nosetests.xml
45+
coverage.xml
46+
*,cover
47+
48+
.vscode
49+
50+
# virtual env
51+
venv/
52+
# python 3 virtual env
53+
python3/
54+
55+
*.env
56+
.env
57+
58+
# resources
59+
resources/output.wav
60+
61+
docs/_build/
62+
deploy.sh
63+
docs/apis
64+
docs/gh-pages
65+
test/__init__.py
66+
*~
67+
68+
.sfdx/tools/apex.db
69+
.pytest_cache/
70+
71+
# openapi-sdkgen
72+
.openapi-generator/
73+
.openapi-generator-ignore
74+
/.pydevproject
75+
/.settings/

‎.pre-commit-config.yaml

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
# This is an example configuration to enable detect-secrets in the pre-commit hook.
2+
# Add this file to the root folder of your repository.
3+
#
4+
# Read pre-commit hook framework https://pre-commit.com/ for more details about the structure of config yaml file and how git pre-commit would invoke each hook.
5+
#
6+
# This line indicates we will use the hook from ibm/detect-secrets to run scan during committing phase.
7+
# Whitewater/whitewater-detect-secrets would sync code to ibm/detect-secrets upon merge.
8+
repos:
9+
- repo: https://github.com/ibm/detect-secrets
10+
# If you desire to use a specific version of detect-secrets, you can replace `master` with other git revisions such as branch, tag or commit sha.
11+
# You are encouraged to use static refs such as tags, instead of branch name
12+
#
13+
# Running "pre-commit autoupdate" would automatically updates rev to latest tag
14+
rev: 0.13.1+ibm.32.dss
15+
hooks:
16+
- id: detect-secrets # pragma: whitelist secret
17+
# Add options for detect-secrets-hook binary. You can run `detect-secrets-hook --help` to list out all possible options.
18+
# You may also run `pre-commit run detect-secrets` to preview the scan result.
19+
# when "--baseline" without "--use-all-plugins", pre-commit scan with just plugins in baseline file
20+
# when "--baseline" with "--use-all-plugins", pre-commit scan with all available plugins
21+
# add "--fail-on-non-audited" to fail pre-commit for unaudited potential secrets
22+
args: [--baseline, .secrets.baseline, --use-all-plugins ]

0 commit comments

Comments
 (0)