| A tool to do search by time in GitHub repositories |
|---|
 |
| Azordev's tracking issues and pull request tool |
| 🐞 Report a bug or 🙋♂️ request a feature |
  |
A tool to help you to search at GitHub Issues / Pull Request by time filters.
Sometimes we need search on some repository, old issues or pull request, or simply needs to check the amount of issues closed in a range of time, to check our productivity or the productivity of another developer. This GUI to do search in GitHub using days filters should be easy of use for any person and should allow to you search easily in the time that you want search.
As vanilla javascript project, you can run it of multiple ways, for example u can just open the index.html file in your browser since it not requires a compile process, and you will have already run the project. I propose the following way:
- Visual Studio Code or another code editor (optional)
- Live Server VSCode extension or another extension for live reload
- Open the project as a new workspace in your code editor.
- Start the live server extension.
- Start to develop!
- Vanilla JavaScript
- Vanilla CSS
- Functional programming paradigm
- Simply develop without frameworks, not dependencies, simply deploy, so fast how develop and check in your browser
vscode- Linux/GNU, macOS, Windows
- Love and Passion for code
This is a little project, it requires to apply good practices to maintain simple the code, and for it we need apply a good file structure, creating the necessary modules to do each part of the code easy to modify. By it I have applied the typic "src" structure, where is saved all the code of the project. Except by index.html that is out of src to do more easy the deploy of the APP. In src you will find some interesting folders and files
|
assets: In this folder we place all the graphic resources. If you need to add / use a new image, this is the site. css: Here we save all the styles of the application, doing possible to do multiple css files if is needed and maintaining the order in the code. js: Here we save all the JavaScript code modules that we can import in the index.html file. |
There are some rules that apply when interacting with the project repository. This will allow us to have a standard that any developer can understand. It is important to comply with these rules so that the linting tool allows us to use the repository.
Branch:
Every time an issue is assigned to you, you must create a new branch. This can be done through the command:
git branch <name of branch>
For convenience, the branches should have a defined structure. For example, if the issue is about adding a new feature, the branch should be:
feature/#issuenumber-brief-description-of-the-feature
Suppose we have issue #12 that asks us to add a header to the main page. Then, the branch would be as follows:
feature/#12-add-header-to-main-page
If it is about solving a bug, we just have to put the word "fix" in front of it. For example:
fix/#14-remove-bad-media-queries-in-rating-component
Commits:
Like branches, commits must also follow a format. Notice how the commit message varies if it is a feature or a bug fix.
feat: added header to main page
fix: removed bad media queries in rating component
Pull Request (PR):
The PR’s are requests that as developers we make once the solution of an issue is completed and we want the code to be integrated into the master branch of the project. Before that, we must ensure that our code is fully functional and adhering to best practices.
Once we have done a commit & push in our branch, a notification with a yellow background will appear in the github repository and will ask us to continue with the PR. In the TextArea to perform the PR you will find several sections that you want to complete: A brief description of what you did, a snapshot (if applicable), the tasks that were completed and the steps to view them.
| Israel Laguan |  Email me to [email protected] /  Connect to my Linkedin |
|---|---|
 |
|
| Victor Peña | Email me to [email protected] / Connect to my Linkedin |
 |
|
| Emmanuel Azócar | Email me to [email protected] |
 |
|
| Angelica Molina | Email me to [email protected] |
 |
🤝 Contributions, issues and feature requests are welcome! Feel free to check the issues page.
🤗 Give a ⭐️ if you like this project!
- https://blog.logrocket.com/deep-dive-into-lefthook-react-native/
- https://blog.logrocket.com/build-robust-react-app-husky-pre-commit-hooks-github-actions/
- Favicon from favicon.io
- https://www.seoptimer.com/meta-tag-generator
- https://dev.to/nitzano/linting-docker-containers-2lo6?utm_source=lefthook
📝 This project is licensed under the Apache 2
Feel free to fork this project and improve it!