It is important that each and every component that is in DDT is at a professional level. To ensure that we create code that is at this standard there is a requirement to validate and upgrade each component against a known baseline that has been created by your project leads. As the lead of this card, it is your responsibility to ensure that you adhere to the practices outlined to ensure it meets the required standard before attempting to create a pull request.
At any time, you request assistance in the development of this card. However, be reminded that any assistance provided to you is done so by another student achieving their own grades. Simply select “Help” under the automations section of this card.
Each card has a designated “lead contributor”. This lead contributor is responsible for ensuring the tasks completion within its allocated time frame. Should other students wish to join you, this is your responsibility to either approve or reject. To become the lead of this task you must be the first person to “Start Work”. To relinquish this title at any time, select “Stop Work”. The lead of this card will become the next sequential person to “Start Work”. It is also your responsibility to ensure you appropriately document your contribution to this card within activity log and via commits to our GitHub repository. Please consult our project mentor if you need assistance in evaluating your contributions against a target grade.
When a branch has been created you must associate it with this card. Once you have completed work (indicated by raising a pull request (whether approved or not)) please select “Complete”. You will need to periodically check GitHub to complete any required actions.
Name of Feature
Baseline Bug fix for Crackmapexec
Priority
Low
Categories
UI
Description of Feature
It is important that each and every component that is in DDT is at a professional level. To ensure that we create code that is at this standard there is a requirement to validate and upgrade each component against a known baseline that has been created by your project leads. As the lead of this card, it is your responsibility to ensure that you adhere to the practices outlined to ensure it meets the required standard before attempting to create a pull request.
At any time, you request assistance in the development of this card. However, be reminded that any assistance provided to you is done so by another student achieving their own grades. Simply select “Help” under the automations section of this card.
Each card has a designated “lead contributor”. This lead contributor is responsible for ensuring the tasks completion within its allocated time frame. Should other students wish to join you, this is your responsibility to either approve or reject. To become the lead of this task you must be the first person to “Start Work”. To relinquish this title at any time, select “Stop Work”. The lead of this card will become the next sequential person to “Start Work”. It is also your responsibility to ensure you appropriately document your contribution to this card within activity log and via commits to our GitHub repository. Please consult our project mentor if you need assistance in evaluating your contributions against a target grade.
When a branch has been created you must associate it with this card. Once you have completed work (indicated by raising a pull request (whether approved or not)) please select “Complete”. You will need to periodically check GitHub to complete any required actions.