-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
also deploy to gitlab darpa ai cyber distribution
- Loading branch information
Showing
7 changed files
with
172 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,39 @@ | ||
# Merge Request for InfoSec Blueprints | ||
|
||
In the virtual sprawl of our project, your code merges with the digital tapestry, a symphony of bytes and logic. | ||
|
||
## Synopsis of Changes | ||
|
||
Detail your odyssey through the code, the alterations and enhancements you've woven into the fabric of our project. | ||
|
||
- Modifications: | ||
- [ ] New digital constructs birthed in the labyrinth of our codebase? | ||
- [ ] Refinements to the existing digital framework? | ||
- [ ] Perhaps a departure, a removal of outdated algorithms or code? | ||
|
||
## Testing the New Paradigms | ||
|
||
Share the trials of your code, the virtual battlegrounds where it was tested, ensuring its harmony with our digital ecosystem. | ||
|
||
- Testing: | ||
- [ ] Environments where the code was tested. | ||
- [ ] Automated processes verifying the integrity of your creation. | ||
|
||
## Linking Threads of Thought | ||
|
||
Connect your work to the larger narrative, the ongoing saga of our project. Reference related issues or prior discussions that sparked this innovation. | ||
|
||
- Related Issues/PRs: | ||
- [ ] Links to related issues or prior pull requests. | ||
|
||
## Adherence to the Digital Ethos | ||
|
||
Our project is a collective dream, a shared digital space. Confirm your adherence to our ethos and practices. | ||
|
||
- [ ] I have read and aligned with the [CONTRIBUTING.md](CONTRIBUTING.md). | ||
- [ ] My code melds with the stylistic essence of this project. | ||
- [ ] I ensure that my contributions enhance, not disrupt, our digital symphony. | ||
|
||
Awaiting your contribution to this cybernetic tapestry, where code and creativity intertwine, enriching the **InfoSec Blueprints**. | ||
|
||
Thank you for being a weaver in our shared digital dream. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
# Bug Report | ||
|
||
## Summary | ||
<!-- Provide a brief and clear summary of the bug. --> | ||
|
||
## Description | ||
<!-- Describe the bug in detail, including the expected and actual behavior. --> | ||
|
||
## Reproduction Steps | ||
<!-- Outline the steps to reproduce the bug. --> | ||
|
||
1. | ||
2. | ||
3. | ||
|
||
## Additional Information | ||
<!-- Add any additional information you think is relevant, such as screenshots, error messages, or system configuration. --> | ||
|
||
## Proposed Solution | ||
<!-- If you have any suggestions for how to fix the bug, please provide them here. | ||
Otherwise, leave this section blank. --> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
# Custom Issue | ||
|
||
## Summary | ||
<!-- Provide a short summary of the issue. --> | ||
|
||
## Description | ||
<!-- Elaborate on the issue, its context, and any relevant details. --> | ||
|
||
## Steps to Reproduce | ||
<!-- If applicable, outline the steps to reproduce the issue. --> | ||
|
||
1. | ||
2. | ||
3. | ||
|
||
## Expected Behavior | ||
<!-- Describe what you expected to happen when encountering this issue. --> | ||
|
||
## Actual Behavior | ||
<!-- Describe the actual behavior you observed. --> | ||
|
||
## Additional Information | ||
<!-- Include any supplementary information, such as screenshots or logs. --> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,17 @@ | ||
# Feature Request | ||
|
||
## Summary | ||
<!-- Provide a concise summary of the feature you're requesting. --> | ||
|
||
## Description | ||
<!-- Describe the feature in detail, including its purpose and any potential benefits it would bring. --> | ||
|
||
## Use Case | ||
<!-- Explain how this feature would be used in practical scenarios. --> | ||
|
||
## Additional Information | ||
<!-- Add any additional context or information that might help in understanding and implementing the feature. --> | ||
|
||
## Proposed Implementation | ||
<!-- If you have any ideas on how this feature could be implemented, please share them here. | ||
Otherwise, leave this section blank. --> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
# Label Configuration for InfoSec Blueprints | ||
# In the coded realm of our project, labels are the signposts, guiding us through the digital fog. | ||
|
||
labels: | ||
- name: "cyber-enhancement" | ||
description: "Proposals for new features or enhancements." | ||
color: "#428BCA" | ||
|
||
- name: "neural-bug" | ||
description: "Identified glitches in the matrix, awaiting rectification." | ||
color: "#FF0000" | ||
|
||
- name: "digital-refactoring" | ||
description: "Improvements to the existing code structure." | ||
color: "#FEDCBA" | ||
|
||
- name: "virtual-documentation" | ||
description: "Updates and enhancements to the project's digital lexicon." | ||
color: "#0E8A16" | ||
|
||
- name: "net-security" | ||
description: "Security improvements and fixes." | ||
color: "#FBCA04" | ||
|
||
# These labels are the beacons in our cybernetic world, categorizing and guiding our digital endeavors. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
# Custom Merge Request Template | ||
|
||
## Summary | ||
<!-- Briefly summarize the purpose and context of this merge request. --> | ||
|
||
## Description | ||
<!-- Provide a detailed description of the changes introduced by this merge request. --> | ||
|
||
## Motivation | ||
<!-- Explain the motivation behind these changes. Why are they necessary? --> | ||
|
||
## Testing | ||
<!-- Describe the testing process, including any test cases or scenarios you've considered. --> | ||
|
||
## Checklist | ||
<!-- Ensure that all the following items are completed before submitting the merge request: --> | ||
|
||
- [ ] Code has been tested thoroughly. | ||
- [ ] Documentation has been updated (if applicable). | ||
- [ ] All tests pass. | ||
- [ ] The code follows the project's coding standards. | ||
|
||
## Reviewer Notes | ||
<!-- Provide guidance or specific instructions for reviewers, if necessary. --> | ||
|
||
<!-- Remember to assign reviewers and label the merge request appropriately before submitting. --> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
# Merge Request | ||
|
||
## Summary | ||
<!-- Provide a brief summary of the changes introduced by this merge request. --> | ||
|
||
## Description | ||
<!-- Describe in detail the purpose and context of this merge request. --> | ||
|
||
## Related Issues | ||
<!-- Link to any related issues, tasks, or discussions. --> | ||
|
||
## Checklist | ||
<!-- Ensure that all the following items are completed before submitting the merge request: --> | ||
|
||
- [ ] Code has been tested locally. | ||
- [ ] Documentation has been updated (if necessary). | ||
- [ ] All tests pass. | ||
- [ ] The code follows the project's coding standards. | ||
|
||
## Additional Notes | ||
<!-- Provide any additional information or context that may be relevant to reviewers. --> |