-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
📔 nnist-pt-20230125 #1
Comments
well, sure. lets have those too and see how we behave, if we prefer a prebuilt barebones template, interchangeble sample template, or building it our own way using smaller templated components. but as much as possible we want uniformity and standardisation "in style-by style" 😎 |
Main Common Components:Cover Templates
Interchangeables:
Chapter Templates
|
oh my head AtomsList of Atoms
MoleculesOrganismsTemplates (a.k.a. Barebones)Cover Templates
Chapter Templates
Other Issue Templates... Pull Request Templates... Pages (a.k.a. Samples) |
i think for the pull request template. i would like a reminder to check if im merging to the correct branch, and / or also with the correct branch. |
think this would be a great reminder for the pull requests in my projects 🤔 which would make me double check if im merging to the correct branch, and with the correct branch. |
we can implement instead an action for every creation of pull request as its dispatcher. but tbh normally i dont add anything in prs, and it seems empty. i think having em as templates would be faster cuz the action might take longer since it still gets dispatched and needs to run, while having them directly on templates would be rather instant. it would be like having a communication with github, treatin em like a friend u know who watchin yo back 😅 ? nah we just lonely 🤡 |
honestly if we implement a github action pr checker, we could have these options randomised - more dynamic and fun. but were just starting out. lets stick with the first one for now. make this a future project instead. we made a project like this before also. https://github.com/nejilabs/colbyfayock-cgaingajt-20210205 |
For Linking Issues in PRs
otherwise u can manually link them after. |
this is the pr temp i came up with 🤣 : Guardian Ugandan KnucklesEnters: The Wise Guardian Ugandan Knuckles...1 - Double Check - Triple CheckCheck if you are merging to the correct branch. And with the Correct Branch pls. 🙏 2 - For Linking Issues in PRs
otherwise u can manually link them after. 👍 Have anything to say to dear ol'guardian ugandan knuckles?For Merging...
Anything else to declare? (Short Description of PR and Affected Issues)
|
@newojima make feature request & bug issues temps |
done |
as for the "componentalised" templates. nah just get them from the samples or barebone templates ^^ |
https://engineeringfordatascience.com/posts/gitmoji/ ooo this would be cool. adding emojis to commit messages would be really nice. |
ok so cuz in the future once we perfected the design of this for project template with nejilab's research projects, well transfer this repo or perhaps create a new one based on this to nejima-kaihatsu (https://github.com/nejima-kaihatsu) where we will establish that repo as the "universal project template" which is forked to its subsidiaries and suited with their according branding for their own projects. the forks then will get the master branch version of the universal project template whenever theres gonna be a massive change to the standard design for all our projects shared among all of us. thus called "universal" so did these tests:
|
perhaps in the future we can implement github actions useful for our projects. but thats in the future. for now, we call this a major success for a brighter future! |
actually i think its best we create a new repo to @nejima-kaihatsu instead of transferring this repo there and change it accordingly. for documentation purposes? afterall this is counted as a research project for experiment. |
dont u think itll be better to just merge the cover issue and cover readme template designs. then by default well just comment out the notes section. cuz usually we compile the notes at the end of the project, while we take the quick dirty notes using the github issues along the project cover tracker issue. |
implemented new colors and varying emojis for project status: <!-- Start: Status | Color Palette Source: https://www.astrouxds.com/img/patterns/status-system-fundamentals.png
✨TODO - 2dccff,
🚧ONGOING - ffb302
✔️DONE - 56f000
⏳STANDBY - 964B00,
❌CANCELLED - ff3838,
💀FAILED - 9ea7ad
-->
<img src="https://img.shields.io/badge/.-9ea7ad?style=for-the-badge"><img src="https://img.shields.io/badge/💀FAILED -333333?style=for-the-badge">
<!-- End: Status --> |
nnist-pt-20230125
Nejilabs NIST Project Template
Description: Nejilabs NIST Project Template used to generate NIST projects along with a standardised design for README.md notes, issues and pull request templates.
In the long term, after we further develop and perfected this project template in Nejilabs, we then move thi project template repo to https://github.com/nejima-kaihatsu (parent).
We then develop that repo to be known as the "Universal Project Template", where it shall dictate the standards and stuff of what projects under the Nejima Group should have (issue & pr templates, common actions and workflows, etc.).
The Universal Project template shall then be shared / forked to its subsidiaries to generate their projects from, while adapting to the branding specs of each according subsidiary.
Project Todos
Project Contents
1- Core Templates
2 - General Templates
Project Notes
Table of Contents
......
The text was updated successfully, but these errors were encountered: