📌 Request: Please Review Important Discussion Before Merge

[pwgit-create]

Dear @lilstiffy ,

As we're approaching the final stages of our merge from develop to master, I'd like to request your urgent
attention on an important discussion. Could you please review and provide feedback on this GitHub discussion:
https://github.com/orgs/pwssOrg/discussions/53 ✅

What's the Plan?

1. Review and Complete PRs: Ensure that the Pull Requests (PRs) for the 3 non-Spring tickets are reviewed and
   moved to the 'Done' column.
2. Copy Tickets to New Repository:
   • Once the PRs are complete, copy the database folder to a new repository created within the PWSS organization.
   • This new repository will be ruled by Stefan and should have a name that somehow links to the File Integrity
     Scanner.
3. Final Commit: Make a last commit stating that ticket 30, 8, and 40 have moved to the new repository.
4. Delete DB Folder: Remove the DB folder from the File-Integrity-Scanner repository.

By following these steps:

• Stefan's commit history will be visible in the master branch while maintaining modularity across the PWSS
  organization.

Please review the discussion linked above, and let me know if you have any questions or need further
clarification. Your input is crucial to ensure we proceed smoothly with this merge.

Thank you for your time and attention!

[pwgit-create]

How to Create a New Repository in the PWSS Organization

Creating a new repository within the PWSS organization is straightforward. Follow these simple steps:

Step 1: Navigate to GitHub Organization

1. Go to https://github.com/pwssOrg.
2. Sign in if you're not already logged in.

Step 2: Create a New Repository

1. Click on the "Repositories" tab.
2. Click on the green "New" button.
3. Choose between creating a repository from scratch or importing code from another location (in this case, we'll
   start from scratch).

Step 3: Fill in Details

• Repository Name: Choose a name that is descriptive and relates to the File Integrity Scanner. For example:

  • File-Integrity-Database
  • FIS-DB-Manager

• Description: Provide a brief description of what this repository will contain. Example:

  Repository for managing the database related to the File Integrity Scanner (FIS) project within PWSS organization. 

Step 4: Configure Settings

1. Choose "Private" .
2. Initialize with a README (optional, but recommended).

Step 5: Create Repository

Click the green "Create repository" button to finalize.

---

Moving the Database Folder

To move the DB folder from the File-Integrity-Scanner repository into the new repository:

1. Clone Repositories:

   • Clone both repositories (File-Integrity-Scanner and your newly created repo) locally.

     git clone https://github.com/pwssOrg/File-Integrity-Scanner.git
     git clone https://github.com/pwssOrg/File-Integrity-Database.git  # or the name you chose

2. Copy DB Folder:

   • Navigate to your local File-Integrity-Scanner repository:

     cd File-Integrity-Scanner

   • Copy the Database folder to the new repository:

     cp -r database /File-Integrity-Database-Repository-Folder/

3. Push Changes:

   • Navigate to your local new repository (e.g., File-Integrity-Database or something similar):

     cd yourpath_to_/File-Integrity-Database-Repository-Folder/

   • Add, commit, and push the changes:

     git add Database
     git commit -S -m "Add DB folder from File-Integrity-Scanner"
     git push origin main  # or master depending on your default branch

4. Clean Up:

   • Remove the Database folder from the File-Integrity-Scanner repository:

     cd ../File-Integrity-Scanner/
     rm -rf Databse

   • Commit and push these changes:

     git commit  -a -S -m "Remove DB folder moved to File-Integrity-Database"
     git branch cleanup
     git push origin cleanup

By following these steps, you'll have successfully created a new repository within the PWSS organization and moved
the database folder from one repo to another.

---

The -a Flag in git commit

The -a (or --all) option in git commit tells Git to automatically stage files that have been modified and
deleted, but not new files. It is essentially a shortcut for git add -u followed by git commit.

However, it's important to note:

• Modified and deleted files are staged.
• New files (those previously untracked) will not be included.

For example:

git commit -a -m "Updated README with new information"

The -S Flag for Signed Commits

The -S flag in git commit is used to sign the commit using GPG (GNU Privacy Guard). This ensures that the
commit is cryptographically signed, providing a layer of security and authenticity. Signing commits is
particularly important for maintaining integrity and accountability within an organization.

Here's how you typically use it:

git commit -S -m "Add DB folder from File-Integrity-Scanner"

In this case:

• -S tells Git to sign the commit with your GPG key.
• -m provides a commit message.

Combining Both

If you want to stage all modified and deleted files, sign the commit, and add a commit message in one line:

git commit -a -S -m "Updated README with new information"

This command stages all changed files (except untracked ones), signs the commit, and adds the specified commit
message.

Important Points

• Verification: Team members can verify signed commits by checking the commit metadata on platforms like
  GitHub or using git log with appropriate flags.