-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Adjust quick install guide since we are making a repository on the fly #21
Conversation
After verifying if we put it into wanted folders and if it works, automation builds upon changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So we want to have README generated via Github actions? |
Automating the documentation is part of the project, since brand name issues or and compatibility remain concern within the community. Seemed prudent to use brand as naming convention. $filename --dev uses lib/$filename/* Use case Primarily for later error handling. Where to direct the documentation, was unclear, so an option or Placeholder was made. Issue #20 cleared so that question A test to Redirecting all generated to share/doc/$filename/ works locally can delete the whole folder and armbian-configng will make folder share/doc/armbian-config Naming conventionsFor exampleln -s armbian-configng armbian-configng-dev
cp -r lib/armbian-configng lib/armbian-configng-dev
sudo armbian-configng-dev -h will try and use
Alternatively
|
Not really, Was originally intended to have separate readme per The doc generators can be easily directed to the share/doc folder now. |
ok. merging this? |
Yes. Ran fine on a codespace. Not sure, about the ci/cd. I only spent few days to get familiar with what a ci/cd pipeline is. |
CI complains about the SheelCheck inconsistency and that has to be taken into account. For future. I also need to add to skip non bash files. |
After verifying if we put it into wanted folders and if it works, automation builds upon changes.