Skip to content

Commit 5feceda

Browse files
PDowneyPDowney
authored
Line Endings
1 parent 5e59708 commit 5feceda

11 files changed

Lines changed: 467 additions & 467 deletions

‎.github/CODE_OF_CONDUCT.md‎

Lines changed: 56 additions & 56 deletions
Original file line numberDiff line numberDiff line change
@@ -1,57 +1,57 @@
1-
# Contributor Covenant Code of Conduct
2-
3-
## Our Pledge
4-
5-
We as members, contributors, and leaders pledge to make participation in our
6-
community a harassment-free experience for everyone, regardless of age, body
7-
size, visible or invisible disability, ethnicity, sex characteristics, gender
8-
identity and expression, level of experience, education, socio-economic status,
9-
nationality, personal appearance, race, religion, or sexual identity and orientation.
10-
11-
We pledge to act and interact in ways that contribute to an open, welcoming,
12-
diverse, inclusive, and healthy community.
13-
14-
## Our Standards
15-
16-
Examples of behavior that contributes to a positive environment for our community include:
17-
18-
* Demonstrating empathy and kindness toward other people
19-
* Being respectful of differing opinions, viewpoints, and experiences
20-
* Giving and gracefully accepting constructive feedback
21-
* Accepting responsibility and apologizing to those affected by our mistakes
22-
* Focusing on what is best for the overall community
23-
24-
Examples of unacceptable behavior include:
25-
26-
* The use of sexualized language or imagery, and sexual attention or advances
27-
* Trolling, insulting or derogatory comments, and personal or political attacks
28-
* Public or private harassment
29-
* Publishing others' private information without explicit permission
30-
* Other conduct which could reasonably be considered inappropriate in a professional setting
31-
32-
## Enforcement Responsibilities
33-
34-
Project maintainers are responsible for clarifying and enforcing our standards of
35-
acceptable behavior and will take appropriate and fair corrective action in
36-
response to any behavior that they deem inappropriate, threatening, offensive,
37-
or harmful.
38-
39-
## Scope
40-
41-
This Code of Conduct applies within all community spaces, and also applies when
42-
an individual is officially representing the community in public spaces.
43-
44-
## Enforcement
45-
46-
Instances of abusive, harassing, or otherwise unacceptable behavior may be
47-
reported to the project maintainers responsible for enforcement at
48-
peter@visistruct.com.
49-
50-
Project maintainers will review and investigate all complaints, and will
51-
respond in a way that they deem appropriate to the circumstances.
52-
53-
## Attribution
54-
55-
This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org),
56-
version 2.1, available at
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
We as members, contributors, and leaders pledge to make participation in our
6+
community a harassment-free experience for everyone, regardless of age, body
7+
size, visible or invisible disability, ethnicity, sex characteristics, gender
8+
identity and expression, level of experience, education, socio-economic status,
9+
nationality, personal appearance, race, religion, or sexual identity and orientation.
10+
11+
We pledge to act and interact in ways that contribute to an open, welcoming,
12+
diverse, inclusive, and healthy community.
13+
14+
## Our Standards
15+
16+
Examples of behavior that contributes to a positive environment for our community include:
17+
18+
* Demonstrating empathy and kindness toward other people
19+
* Being respectful of differing opinions, viewpoints, and experiences
20+
* Giving and gracefully accepting constructive feedback
21+
* Accepting responsibility and apologizing to those affected by our mistakes
22+
* Focusing on what is best for the overall community
23+
24+
Examples of unacceptable behavior include:
25+
26+
* The use of sexualized language or imagery, and sexual attention or advances
27+
* Trolling, insulting or derogatory comments, and personal or political attacks
28+
* Public or private harassment
29+
* Publishing others' private information without explicit permission
30+
* Other conduct which could reasonably be considered inappropriate in a professional setting
31+
32+
## Enforcement Responsibilities
33+
34+
Project maintainers are responsible for clarifying and enforcing our standards of
35+
acceptable behavior and will take appropriate and fair corrective action in
36+
response to any behavior that they deem inappropriate, threatening, offensive,
37+
or harmful.
38+
39+
## Scope
40+
41+
This Code of Conduct applies within all community spaces, and also applies when
42+
an individual is officially representing the community in public spaces.
43+
44+
## Enforcement
45+
46+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
47+
reported to the project maintainers responsible for enforcement at
48+
peter@visistruct.com.
49+
50+
Project maintainers will review and investigate all complaints, and will
51+
respond in a way that they deem appropriate to the circumstances.
52+
53+
## Attribution
54+
55+
This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org),
56+
version 2.1, available at
5757
[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html).

‎.github/CONTRIBUTING.md‎

Lines changed: 85 additions & 85 deletions
Original file line numberDiff line numberDiff line change
@@ -1,86 +1,86 @@
1-
# Contributing to EngineScript
2-
3-
Thank you for your interest in contributing to EngineScript! This document provides guidelines and information for contributors.
4-
5-
## Table of Contents
6-
- [Code of Conduct](#code-of-conduct)
7-
- [How Can I Contribute?](#how-can-i-contribute)
8-
- [Development Setup](#development-setup)
9-
- [Pull Request Process](#pull-request-process)
10-
- [Style Guidelines](#style-guidelines)
11-
12-
## Code of Conduct
13-
14-
This project follows our [Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code.
15-
16-
## How Can I Contribute?
17-
18-
### Reporting Bugs
19-
- Check if the bug has already been reported in [Issues](https://github.com/EngineScript/EngineScript/issues)
20-
- If not, create a new issue with a clear title and description
21-
- Include steps to reproduce, expected behavior, and actual behavior
22-
- Add relevant system information (OS, PHP version, etc.)
23-
24-
### Suggesting Enhancements
25-
- First, read the [documentation](README.md)
26-
- Check if the enhancement has been suggested in [Issues](https://github.com/EngineScript/EngineScript/issues)
27-
- Provide a clear and detailed explanation of the feature
28-
29-
### Pull Requests
30-
1. Fork the repository
31-
2. Create a new branch (`git checkout -b feature/your-feature`)
32-
3. Make your changes
33-
4. Run tests if available
34-
5. Commit your changes (`git commit -m 'Add some feature'`)
35-
6. Push to the branch (`git push origin feature/your-feature`)
36-
7. Create a Pull Request
37-
38-
## Development Setup
39-
40-
1. Set up a test environment:
41-
- Ubuntu 24.04 LTS server
42-
43-
## Pull Request Process
44-
45-
1. Update the README.md with details of changes if applicable
46-
2. Update the documentation if you're changing functionality
47-
3. Use semantic commit messages:
48-
- `feat:` for new features
49-
- `fix:` for bug fixes
50-
- `docs:` for documentation changes
51-
- `style:` for formatting changes
52-
- `refactor:` for code restructuring
53-
- `test:` for adding tests
54-
- `chore:` for maintenance tasks
55-
56-
## Style Guidelines
57-
58-
### Shell Scripts
59-
- Use 2 spaces for indentation
60-
- Add comments for complex logic
61-
- Use meaningful variable names
62-
- Always check return values
63-
- Use shellcheck for validation
64-
65-
### Configuration Files
66-
- Use proper indentation
67-
- Add comments for non-obvious settings
68-
- Keep related settings grouped together
69-
- Follow the existing format
70-
71-
### Documentation
72-
- Use clear, concise language
73-
- Include examples where appropriate
74-
- Keep formatting consistent
75-
- Update table of contents when needed
76-
77-
## Need Help?
78-
79-
Feel free to:
80-
- Check our [documentation](README.md)
81-
- Open an [issue](https://github.com/EngineScript/EngineScript/issues)
82-
- Join our discussions
83-
84-
## License
85-
1+
# Contributing to EngineScript
2+
3+
Thank you for your interest in contributing to EngineScript! This document provides guidelines and information for contributors.
4+
5+
## Table of Contents
6+
- [Code of Conduct](#code-of-conduct)
7+
- [How Can I Contribute?](#how-can-i-contribute)
8+
- [Development Setup](#development-setup)
9+
- [Pull Request Process](#pull-request-process)
10+
- [Style Guidelines](#style-guidelines)
11+
12+
## Code of Conduct
13+
14+
This project follows our [Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code.
15+
16+
## How Can I Contribute?
17+
18+
### Reporting Bugs
19+
- Check if the bug has already been reported in [Issues](https://github.com/EngineScript/EngineScript/issues)
20+
- If not, create a new issue with a clear title and description
21+
- Include steps to reproduce, expected behavior, and actual behavior
22+
- Add relevant system information (OS, PHP version, etc.)
23+
24+
### Suggesting Enhancements
25+
- First, read the [documentation](README.md)
26+
- Check if the enhancement has been suggested in [Issues](https://github.com/EngineScript/EngineScript/issues)
27+
- Provide a clear and detailed explanation of the feature
28+
29+
### Pull Requests
30+
1. Fork the repository
31+
2. Create a new branch (`git checkout -b feature/your-feature`)
32+
3. Make your changes
33+
4. Run tests if available
34+
5. Commit your changes (`git commit -m 'Add some feature'`)
35+
6. Push to the branch (`git push origin feature/your-feature`)
36+
7. Create a Pull Request
37+
38+
## Development Setup
39+
40+
1. Set up a test environment:
41+
- Ubuntu 24.04 LTS server
42+
43+
## Pull Request Process
44+
45+
1. Update the README.md with details of changes if applicable
46+
2. Update the documentation if you're changing functionality
47+
3. Use semantic commit messages:
48+
- `feat:` for new features
49+
- `fix:` for bug fixes
50+
- `docs:` for documentation changes
51+
- `style:` for formatting changes
52+
- `refactor:` for code restructuring
53+
- `test:` for adding tests
54+
- `chore:` for maintenance tasks
55+
56+
## Style Guidelines
57+
58+
### Shell Scripts
59+
- Use 2 spaces for indentation
60+
- Add comments for complex logic
61+
- Use meaningful variable names
62+
- Always check return values
63+
- Use shellcheck for validation
64+
65+
### Configuration Files
66+
- Use proper indentation
67+
- Add comments for non-obvious settings
68+
- Keep related settings grouped together
69+
- Follow the existing format
70+
71+
### Documentation
72+
- Use clear, concise language
73+
- Include examples where appropriate
74+
- Keep formatting consistent
75+
- Update table of contents when needed
76+
77+
## Need Help?
78+
79+
Feel free to:
80+
- Check our [documentation](README.md)
81+
- Open an [issue](https://github.com/EngineScript/EngineScript/issues)
82+
- Join our discussions
83+
84+
## License
85+
8686
By contributing to EngineScript, you agree that your contributions will be licensed under the same terms as the project.

‎.github/FUNDING.yml‎

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,9 @@
1-
# These are supported funding model platforms
2-
3-
#patreon: # Replace with a single Patreon username
4-
5-
github: enginescript
6-
ko_fi: enginescript
7-
buy_me_a_coffee: enginescript
8-
liberapay: enginescript
1+
# These are supported funding model platforms
2+
3+
#patreon: # Replace with a single Patreon username
4+
5+
github: enginescript
6+
ko_fi: enginescript
7+
buy_me_a_coffee: enginescript
8+
liberapay: enginescript
99
thanks_dev: gh/pdowney

‎.github/workflows/branch-cleanup.yml‎

Lines changed: 44 additions & 44 deletions
Original file line numberDiff line numberDiff line change
@@ -1,45 +1,45 @@
1-
name: Branch Cleanup
2-
3-
on:
4-
pull_request:
5-
types: [closed]
6-
7-
permissions:
8-
contents: write
9-
pull-requests: read
10-
11-
jobs:
12-
cleanup:
13-
runs-on: ubuntu-latest
14-
15-
steps:
16-
- uses: actions/checkout@v4
17-
with:
18-
fetch-depth: 0
19-
token: ${{ secrets.GITHUB_TOKEN }}
20-
21-
- name: Delete merged branch
22-
if: github.event.pull_request.merged == true
23-
env:
24-
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
25-
run: |
26-
branch="${{ github.event.pull_request.head.ref }}"
27-
repo="${{ github.repository }}"
28-
29-
echo "Checking branch: $branch"
30-
31-
# Protected branch check
32-
if [[ "$branch" =~ ^(main|master|dev|develop|staging|production)$ ]]; then
33-
echo "::warning::Skipping deletion of protected branch: $branch"
34-
exit 0
35-
fi
36-
37-
# Attempt branch deletion
38-
echo "Attempting to delete branch: $branch"
39-
if git push origin --delete "$branch" 2>/dev/null; then
40-
echo "::notice::Successfully deleted branch: $branch"
41-
else
42-
echo "::error::Failed to delete branch: $branch"
43-
exit 1
44-
fi
1+
name: Branch Cleanup
2+
3+
on:
4+
pull_request:
5+
types: [closed]
6+
7+
permissions:
8+
contents: write
9+
pull-requests: read
10+
11+
jobs:
12+
cleanup:
13+
runs-on: ubuntu-latest
14+
15+
steps:
16+
- uses: actions/checkout@v4
17+
with:
18+
fetch-depth: 0
19+
token: ${{ secrets.GITHUB_TOKEN }}
20+
21+
- name: Delete merged branch
22+
if: github.event.pull_request.merged == true
23+
env:
24+
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
25+
run: |
26+
branch="${{ github.event.pull_request.head.ref }}"
27+
repo="${{ github.repository }}"
28+
29+
echo "Checking branch: $branch"
30+
31+
# Protected branch check
32+
if [[ "$branch" =~ ^(main|master|dev|develop|staging|production)$ ]]; then
33+
echo "::warning::Skipping deletion of protected branch: $branch"
34+
exit 0
35+
fi
36+
37+
# Attempt branch deletion
38+
echo "Attempting to delete branch: $branch"
39+
if git push origin --delete "$branch" 2>/dev/null; then
40+
echo "::notice::Successfully deleted branch: $branch"
41+
else
42+
echo "::error::Failed to delete branch: $branch"
43+
exit 1
44+
fi
4545

0 commit comments

Comments
 (0)