Switch to github flow (#117)

Author: mfreeborn

.github/workflows/ci.yml

@@ -1,10 +1,11 @@
 name: CI
 
 on:
-  push:
-    branches: [ dev ]
+  workflow_dispatch:
   pull_request:
-    branches: [ dev ]
+    branches: [ master ]
+  push:
+    branches: [ master ]
 
 # Cancel any in-flight jobs for the same PR/branch so there's only one active
 # at a time

.github/workflows/release.yml

@@ -0,0 +1,28 @@
+name: Deploy Releases
+
+on:
+  push:
+    tags:
+    - '[0-9]+.[0-9]+.[0-9]+'
+
+jobs:
+  create-crates-io-release:
+    name: Deploy to crates.io
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v3
+    - uses: dtolnay/rust-toolchain@stable
+    - run: cargo login ${{ env.CRATES_IO_TOKEN }}
+      env:
+        CRATES_IO_TOKEN: ${{ secrets.CRATES_IO_TOKEN }}
+    - run: cargo publish --allow-dirty -p plotly_derive
+    - run: sleep 10
+    - run: cargo publish --allow-dirty -p plotly_kaleido
+    - run: sleep 10
+    - run: cargo publish --allow-dirty -p plotly
+
+  create-gh-release:
+    name: Deploy to GH Releases
+    runs-on: ubuntu-latest
+    steps:
+      - uses: softprops/action-gh-release@v1

.github/workflows/release_ci.yml

@@ -1,8 +1,7 @@
 # Changelog
 All notable changes to this project will be documented in this file.
 
-The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
-and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/) and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ## [0.8.2] - 2022-11-03
 ### Added

CHANGELOG.md

@@ -1,43 +1,22 @@
 # Contributing to Ploty.rs
 
-Contribution in the form of suggestions, bug reports, pull requests and feedback is welcome from everyone. In this document
-you'll find guidance if you are considering to offer your help to this project.
+Contribution in the form of suggestions, bug reports, pull requests and feedback is welcome from everyone. In this document you'll find guidance if you are considering to offer your help to this project.
 
-## Submitting bug reports and feature requests
+## Submitting Bug Reports and Feature Requests
 
-When reporting a bug or asking for help, please include enough details so that
-the people helping you can reproduce the behavior you are seeing. For some tips
-on how to approach this, read about how to produce a [Minimal, Complete, and
-Verifiable example].
+When reporting a bug or asking for help, please include enough details so that the people helping you can reproduce the behavior you are seeing. For some tips on how to approach this, read about how to produce a [Minimal, Complete, and Verifiable example].
 
 [Minimal, Complete, and Verifiable example]: https://stackoverflow.com/help/mcve
 
-When making a feature request, please make it clear what problem you intend to
-solve with the feature, any ideas for how Plotly.rs could support solving that
-problem, any possible alternatives, and any disadvantages.
+When making a feature request, please make it clear what problem you intend to solve with the feature, any ideas for how  Plotly.rs could support solving that problem, any possible alternatives, and any disadvantages.
 
-## Process
+## Pull Requests
 
-Before spending time and effort in making changes to the library, please open an issue first explaining the proposed change 
-and indicate that you would be happy to implement/fix the issue. Once the utility of the addition is discussed and verified,
-you're welcome to proceed.
+Before spending time and effort in making changes to the library, it's a good idea to discuss it first on the issue tracker to see whether your change is likely to be accepted. 
 
-Fork [plotly](https://igiagkiozis.github.io/plotly/) to your own account and checkout the `dev` branch. Once the bug/feature is complete, make sure you update 
-appropriately the [change log](CHANGELOG.md). 
+Fork [plotly](https://igiagkiozis.github.io/plotly/) to your own account and create a new branch for your feature. Remember to update the [changelog](CHANGELOG.md) - use previous entries as a template. 
 
-For change-log updates please use previous entries as reference, namely classify
-the nature of the change, e.g. fixed, changed, added etc., and a brief description. The entry in the change-log that should be
-used for the update will always be marked with YEAR-XX-XX, e.g. 2022-XX-XX.
-
-Check that the test suite passes locally and that all examples still execute and produce the expected results before submitting a pull request.
-
-Make a pull request with your changes directly to the `dev` branch. Please note, pull requests to the `master` branch will not
-be considered. The `master` branch is reserved for release.
-
-
-Also, include a description of our changes as documented in the 
-[change-log](CHANGELOG.md); just copy paste these additions in the pull request description. Wait for one of the reviewers 
-to look at your code and either merge it or give feedback which you should adapt to.
+When your contribution is ready for review, make a pull request with your changes directly to the `master` branch. One of the maintainers will have a look at what you've done, suggest any necessary changes and, when everyone is happy, merge the pull request.
 
 ## Code of Conduct
 

CONTRIBUTING.md

@@ -4,7 +4,7 @@ version = "0.8.2"
 description = "A plotting library powered by Plotly.js"
 authors = ["Ioannis Giagkiozis <[email protected]>"]
 license = "MIT"
-readme = "README.md"
+readme = "../README.md"
 homepage = "https://github.com/igiagkiozis/plotly"
 documentation = "https://docs.rs/plotly"
 repository = "https://github.com/igiagkiozis/plotly"