Skip to content

Commit 3eb4e00

Browse files
AptiviCEOAptiviCEO
committed
Merge branch 'main' of https://github.com/Aptivi/NamesList 
2 parents 70ca04f + 80b5b5d commit 3eb4e00

18 files changed

Lines changed: 176627 additions & 229727 deletions

‎.gitattributes‎

Lines changed: 63 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,63 @@
1+
###############################################################################
2+
# Set default behavior to automatically normalize line endings.
3+
###############################################################################
4+
* text=auto
5+
6+
###############################################################################
7+
# Set default behavior for command prompt diff.
8+
#
9+
# This is need for earlier builds of msysgit that does not have it on by
10+
# default for csharp files.
11+
# Note: This is only used by command line
12+
###############################################################################
13+
#*.cs diff=csharp
14+
15+
###############################################################################
16+
# Set the merge driver for project and solution files
17+
#
18+
# Merging from the command prompt will add diff markers to the files if there
19+
# are conflicts (Merging from VS is not affected by the settings below, in VS
20+
# the diff markers are never inserted). Diff markers may cause the following
21+
# file extensions to fail to load in VS. An alternative would be to treat
22+
# these files as binary and thus will always conflict and require user
23+
# intervention with every merge. To do so, just uncomment the entries below
24+
###############################################################################
25+
#*.sln merge=binary
26+
#*.csproj merge=binary
27+
#*.vbproj merge=binary
28+
#*.vcxproj merge=binary
29+
#*.vcproj merge=binary
30+
#*.dbproj merge=binary
31+
#*.fsproj merge=binary
32+
#*.lsproj merge=binary
33+
#*.wixproj merge=binary
34+
#*.modelproj merge=binary
35+
#*.sqlproj merge=binary
36+
#*.wwaproj merge=binary
37+
38+
###############################################################################
39+
# behavior for image files
40+
#
41+
# image files are treated as binary by default.
42+
###############################################################################
43+
#*.jpg binary
44+
#*.png binary
45+
#*.gif binary
46+
47+
###############################################################################
48+
# diff behavior for common document formats
49+
#
50+
# Convert binary document formats to text before diffing them. This feature
51+
# is only available from the command line. Turn it on by uncommenting the
52+
# entries below.
53+
###############################################################################
54+
#*.doc diff=astextplain
55+
#*.DOC diff=astextplain
56+
#*.docx diff=astextplain
57+
#*.DOCX diff=astextplain
58+
#*.dot diff=astextplain
59+
#*.DOT diff=astextplain
60+
#*.pdf diff=astextplain
61+
#*.PDF diff=astextplain
62+
#*.rtf diff=astextplain
63+
#*.RTF diff=astextplain

‎.github/ISSUE_TEMPLATE/ask-a-question.md‎

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
---
2+
name: Ask a question
3+
about: Ask us anything about KS.
4+
title: "[Q&A] [FeatureName] - [Question]"
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
### Type of question
11+
<!-- Select the type of the question that you're going to ask here. -->
12+
- [ ] General
13+
- [ ] API
14+
- [ ] Commands
15+
- [ ] Mods
16+
- [ ] Others
17+
18+
### Question
19+
<!-- Ask us a question here. Be descriptive as much as you can. -->

‎.github/ISSUE_TEMPLATE/report-an-issue.md‎

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
---
2+
name: Report an issue
3+
about: Thank you for reporting a bug to us.
4+
title: "[BUG] [featureName] - [issue]"
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
### Description
11+
<!-- Describe how this bug happened, and general information about it. Note that you need to be as descriptive as possible. -->
12+
13+
14+
### Expected behavior
15+
<!-- How do you expect this program to behave? -->
16+
17+
18+
### Actual behavior
19+
<!-- What did it do instead? -->
20+
21+
22+
### Steps to reproduce
23+
<!-- Provide clear step-by-step instructions about reproducing this bug. -->
24+
1. Open x
25+
1. Write `yyy`
26+
1. Observe a happening instead of z
27+
28+
### Version
29+
<!-- This should be in this format: <Version> (<Commit>) (<Branch>). Commit number and branch required for development builds. -->
30+
Version `0.0.0 0000000000000000000000000000000000000000 main`

‎.github/issue_template.md‎

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
### Description
2+
<!-- Describe how this bug happened, and general information about it. Note that you need to be as descriptive as possible. -->
3+
4+
5+
### Expected behavior
6+
<!-- How do you expect this program to behave? -->
7+
8+
9+
### Actual behavior
10+
<!-- What did it do instead? -->
11+
12+
13+
### Steps to reproduce
14+
<!-- Provide clear step-by-step instructions about reproducing this bug. -->
15+
1. Open x
16+
1. Write `yyy`
17+
1. Observe a happening instead of z
18+
19+
### Version
20+
<!-- This should be in this format: <Version> (<Commit>) (<Branch>). Commit number and branch required for development builds. -->
21+
Version `0.0.0 0000000000000000000000000000000000000000 main`

‎.github/pull_request_template.md‎

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
## Description
2+
<!-- Talk about your pull request. Note that you need to be as descriptive as possible. -->
3+
4+
5+
## Change type
6+
<!-- Specify what kind of changes you made. -->
7+
- [ ] Bug fixes
8+
- [ ] Performance improvements
9+
- [ ] Feature changes
10+
- [ ] Behavioral changes
11+
- [ ] Other (specify)
12+
13+
## Tested?
14+
<!-- Have you tested your changes? -->
15+
- [ ] Yes, I have
16+
- [ ] No, I haven't
17+
- [ ] Not sure
18+
19+
## Other changes?
20+
<!-- Specify the changes that don't fit to the categories above. -->

‎CODE_OF_CONDUCT.md‎

Lines changed: 76 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,76 @@
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, sex characteristics, gender identity and expression,
9+
level of experience, education, socio-economic status, nationality, personal
10+
appearance, race, religion, or sexual identity and 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 eoflaoevicecity AT gmail DOT 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 https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
72+
73+
[homepage]: https://www.contributor-covenant.org
74+
75+
For answers to common questions about this code of conduct, see
76+
https://www.contributor-covenant.org/faq

0 commit comments

Comments
 (0)