-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #39 from bitpredator/main
feat: nuovo flusso di lavoro (test deploy)
- Loading branch information
Showing
2 changed files
with
69 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,45 @@ | ||
# Welcome | ||
|
||
Welcome to the "Italian-Truck-Company" project repository. Thank you for your interest in contributing to the project. Full details and guidelines on how to ensure this project is managed well are included below. | ||
|
||
## Contributing to the project | ||
|
||
As this is an open source project, anyone is free to contribute as much or as little as they like. If you're just getting started with GitHub or project contributions then we suggest you take a look at issues on the repository. These issues will vary in complexity depending on the issue itself. | ||
|
||
If you're comfortable contributing to Open Source projects on GitHub please ensure you read our expectations for issue tracking, feature proposals and pull requests. | ||
|
||
## Testing the project | ||
|
||
If changes are made they should always be tested to make sure they work as intended and don't conflict with other systems. If you see a pull request open it's recommended that you test the features that were implemented to check for errors or it works as intended. | ||
|
||
## Issue Tracking | ||
Please use GitHub issues to track new features or bugs. | ||
|
||
When submitting an issue, there's a few guidelines we'd ask you to respect to make it easier to manage and for others to understand: | ||
* **Search the issue tracker** before you submit your issue - it may already be present. | ||
* When opening an issue, a template is provided for you. Please provide as much information as requested to ensure others are able to act upon the requests or bug report. | ||
* Please ensure you add screenshots or documentation references for bugs/changes so we can quickly ascertain if the request is suitable. | ||
|
||
**In order to be 'assigned' an issue**, please comment on the issue itself letting others know you are working on it. | ||
|
||
## Pull Requests | ||
|
||
We welcome pull requests with fixes and improvements to the project. | ||
|
||
The work-flow for submitting a new pull request is designed to be simple, but also to ensure consistency from **all** contributors: | ||
* Fork the project into your personal space on GitHub.com. | ||
* Add changes to CHANGELOG.md with credits to yourself. | ||
* Commit your changes. | ||
* When writing commit messages make sure they are clear about what has been changed. | ||
* Push the commit(s) to your fork. | ||
* Submit a pull request (PR) to the master branch. | ||
* The PR title should describe the change that has been made. | ||
* Follow the PR template and write as much detail as necessary for your changes and include documents/screenshots if needed. | ||
* Be prepared to answer any questions about your PR when it is reviewed for acceptance. | ||
|
||
**Please** keep your changes in a single PR as small as possible (relating to one issue) as this makes it easier to review and accept. Large PRs with a small error will prevent the entire PR from being accepted. | ||
|
||
## Expectations | ||
As contributors and maintainers of this project, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities. | ||
|
||
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, issues and other contributions that are not aligned to this Code of Conduct. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
name: Test deployment | ||
|
||
on: | ||
pull_request: | ||
branches: | ||
- main | ||
# Review gh actions docs if you want to further define triggers, paths, etc | ||
# https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#on | ||
|
||
jobs: | ||
test-deploy: | ||
name: Test deployment | ||
runs-on: ubuntu-latest | ||
steps: | ||
- uses: actions/checkout@v3 | ||
- uses: actions/setup-node@v3 | ||
with: | ||
node-version: 18 | ||
cache: yarn | ||
|
||
- name: Install dependencies | ||
run: yarn install --frozen-lockfile | ||
- name: Test build website | ||
run: yarn build |