work-workflow-test 0.0.1

package/README.md

@@ -0,0 +1,93 @@
+# workflow
+
+
+
+## Getting started
+
+To make it easy for you to get started with GitLab, here's a list of recommended next steps.
+
+Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
+
+## Add your files
+
+- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
+- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
+
+```
+cd existing_repo
+git remote add origin https://calib.dev/doworks/workflow.git
+git branch -M main
+git push -uf origin main
+```
+
+## Integrate with your tools
+
+- [ ] [Set up project integrations](https://calib.dev/doworks/workflow/-/settings/integrations)
+
+## Collaborate with your team
+
+- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
+- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
+- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
+- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
+- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
+
+## Test and Deploy
+
+Use the built-in continuous integration in GitLab.
+
+- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
+- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
+- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
+- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
+- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
+
+***
+
+# Editing this README
+
+When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
+
+## Suggestions for a good README
+
+Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
+
+## Name
+Choose a self-explaining name for your project.
+
+## Description
+Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
+
+## Badges
+On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
+
+## Visuals
+Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
+
+## Installation
+Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
+
+## Usage
+Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
+
+## Support
+Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
+
+## Roadmap
+If you have ideas for releases in the future, it is a good idea to list them in the README.
+
+## Contributing
+State if you are open to contributions and what your requirements are for accepting them.
+
+For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
+
+You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
+
+## Authors and acknowledgment
+Show your appreciation to those who have contributed to the project.
+
+## License
+For open source projects, say how it is licensed.
+
+## Project status
+If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.

package/dist/arrow.svg

@@ -0,0 +1,3 @@
+<svg width="31" height="8" viewBox="0 0 31 8" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M30.3536 4.35355C30.5488 4.15829 30.5488 3.84171 30.3536 3.64645L27.1716 0.464466C26.9763 0.269204 26.6597 0.269204 26.4645 0.464466C26.2692 0.659728 26.2692 0.976311 26.4645 1.17157L29.2929 4L26.4645 6.82843C26.2692 7.02369 26.2692 7.34027 26.4645 7.53553C26.6597 7.7308 26.9763 7.7308 27.1716 7.53553L30.3536 4.35355ZM0 4V4.5H30V4V3.5H0V4Z" fill="black"/>
+</svg>

package/dist/back_button.svg

@@ -0,0 +1,10 @@
+<svg width="33" height="33" viewBox="0 0 33 33" fill="none" xmlns="http://www.w3.org/2000/svg">
+<rect x="0.746094" y="1" width="31" height="31" rx="3.5" fill="#F4F4F5"/>
+<rect x="0.746094" y="1" width="31" height="31" rx="3.5" stroke="#E9EAEB"/>
+<mask id="mask0_25970_185309" style="mask-type:alpha" maskUnits="userSpaceOnUse" x="0" y="0" width="33" height="33">
+<rect x="0.246094" y="0.5" width="32" height="32" fill="#D9D9D9"/>
+</mask>
+<g mask="url(#mask0_25970_185309)">
+<path d="M18.9141 9.31641C19.2319 9.31646 19.4771 9.41675 19.6699 9.60938C19.8629 9.80231 19.9638 10.0481 19.9639 10.3662C19.9639 10.6845 19.8629 10.9301 19.6699 11.123L14.4707 16.3232L14.2939 16.5L14.4707 16.6768L19.6699 21.877C19.8628 22.0699 19.9638 22.3147 19.9639 22.6328C19.9639 22.9511 19.8629 23.1967 19.6699 23.3896C19.477 23.5824 19.2321 23.6826 18.9141 23.6826C18.5958 23.6826 18.3502 23.5826 18.1572 23.3896L12.0234 17.2559C11.9129 17.1452 11.8402 17.0319 11.7988 16.916C11.7536 16.7895 11.7305 16.6512 11.7305 16.5C11.7305 16.3488 11.7537 16.2105 11.7988 16.084C11.8403 15.968 11.9127 15.854 12.0234 15.7432L18.1572 9.60938C18.3502 9.41654 18.5959 9.31641 18.9141 9.31641Z" fill="#8F949A" stroke="#F4F4F5" stroke-width="0.5"/>
+</g>
+</svg>

package/dist/delete.svg

@@ -0,0 +1,8 @@
+<svg width="17" height="17" viewBox="0 0 17 17" fill="none" xmlns="http://www.w3.org/2000/svg">
+<mask id="mask0_26930_250464" style="mask-type:alpha" maskUnits="userSpaceOnUse" x="0" y="0" width="17" height="17">
+<rect x="0.75" y="1.1875" width="15" height="15" fill="#D9D9D9" stroke="#363F4A"/>
+</mask>
+<g mask="url(#mask0_26930_250464)">
+<path d="M6.83984 3.11035H9.66016C9.82008 3.11035 9.95583 3.16676 10.0684 3.2793C10.181 3.39193 10.2373 3.52762 10.2373 3.6875V3.7002H12.75C12.8885 3.7002 13.0043 3.74642 13.0977 3.83984C13.191 3.93326 13.2373 4.04903 13.2373 4.1875C13.2373 4.32613 13.1911 4.44196 13.0977 4.53516C13.0043 4.62847 12.8885 4.6748 12.75 4.6748H12.5713V13.1484C12.5713 13.4765 12.4543 13.7576 12.2207 13.9912C11.987 14.2249 11.706 14.3418 11.3779 14.3418H5.12207C4.79397 14.3418 4.51297 14.2249 4.2793 13.9912C4.04567 13.7576 3.92871 13.4765 3.92871 13.1484V4.6748H3.75C3.61148 4.6748 3.49566 4.62761 3.40234 4.53418C3.30926 4.4409 3.26277 4.32567 3.2627 4.1875C3.2627 4.04895 3.30903 3.93302 3.40234 3.83984C3.49566 3.74653 3.61148 3.7002 3.75 3.7002H6.2627V3.6875C6.2627 3.52762 6.31905 3.39193 6.43164 3.2793C6.54417 3.16676 6.67992 3.11035 6.83984 3.11035ZM4.9043 13.1484C4.9043 13.2112 4.92483 13.2637 4.96582 13.3047C5.00686 13.3457 5.05924 13.3662 5.12207 13.3662H11.3779C11.4408 13.3662 11.4931 13.3457 11.5342 13.3047C11.5752 13.2637 11.5957 13.2112 11.5957 13.1484V4.6748H4.9043V13.1484ZM7.01855 6.0332C7.15704 6.0332 7.27295 6.07973 7.36621 6.17285C7.45961 6.26625 7.5068 6.38206 7.50684 6.52051V11.5205C7.50684 11.6589 7.46028 11.7748 7.36719 11.8682C7.27388 11.9615 7.15804 12.0078 7.01953 12.0078C6.88091 12.0078 6.7653 11.9615 6.67188 11.8682C6.57855 11.7747 6.53223 11.659 6.53223 11.5205V6.52051C6.53226 6.38205 6.5787 6.26625 6.67188 6.17285C6.76505 6.07981 6.88036 6.0333 7.01855 6.0332ZM9.48047 6.0332C9.61902 6.0332 9.73473 6.07965 9.82812 6.17285C9.92141 6.26625 9.96774 6.38205 9.96777 6.52051V11.5205C9.96777 11.659 9.92134 11.7747 9.82812 11.8682C9.73493 11.9613 9.61971 12.0077 9.48145 12.0078C9.34288 12.0078 9.22708 11.9614 9.13379 11.8682C9.04036 11.7747 8.99316 11.659 8.99316 11.5205V6.52051C8.9932 6.38207 9.03966 6.26624 9.13281 6.17285C9.22612 6.07954 9.34196 6.03321 9.48047 6.0332Z" fill="#363F4A" stroke="#363F4A" stroke-width="0.025"/>
+</g>
+</svg>

package/dist/doworks_icon.svg

@@ -0,0 +1,4 @@
+<svg width="25" height="23" viewBox="0 0 25 23" fill="none" xmlns="http://www.w3.org/2000/svg">
+<path d="M5.40189 22.0101L0.5 12.8309L4.54243 15.5547C5.03397 15.8859 5.69499 15.8008 6.08657 15.3558L12.0652 8.5625L5.40189 22.0101Z" fill="#FB7000"/>
+<path d="M13.2642 21.9883L8.27344 12.7765L12.3444 15.4613C12.8622 15.8028 13.556 15.6848 13.9318 15.1913L24.7478 0.988281L13.2642 21.9883Z" fill="#FB7000"/>
+</svg>