File Template with Copyright Header

[Jag-Marcel]

Contributor checklist

• This pull request is on a separate branch and not the main branch

---

Description

This adds a template to a new directory called ScribeTemplates, which adds the copyright notice used in #403 to any newly created file using said template. You would find it when creating a new file in Xcode, where you would scroll to the bottom and select the template in a new category called "ScribeTemplates".
To use this template, you would first have to add it to your own Xcode templates by:

1. Creating a "Templates" directory in your Xcode folder (found at Users/[your username]/Library/Developer/Xcode)
2. Symlink the Scribe template into "Templates"

Using commands:

mkdir ~/Library/Developer/Xcode/Templates
ln -s [Path to your Scribe directory]/Scribe-iOS/ScribeTemplates ~/Library/Developer/Xcode/Templates/

Related issue

• Edit/add template header for files #405

[github-actions]

Thank you for the pull request!

The Scribe team will do our best to address your contribution as soon as we can. The following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :)

If you're not already a member of our public Matrix community, please consider joining! We'd suggest using Element as your Matrix client, and definitely join the General and iOS rooms once you're in. It'd be great to have you!

Maintainer checklist

• The commit messages for the remote branch should be checked to make sure the contributor's email is set up correctly so that they receive credit for their contribution

  • The contributor's name and icon in remote commits should be the same as what appears in the PR
  • If there's a mismatch, the contributor needs to make sure that the email they use for GitHub matches what they have for git config user.email in their local Scribe-iOS repo

• The CHANGELOG has been updated with a description of the changes for the upcoming release and the corresponding issue (if necessary)

[Jag-Marcel]

I don't know if there is a way to create the link automatically when cloning / running the project for the first time, otherwise we'd have to add a note about this to README.md

[andrewtavis]

Thanks for this, @Jag-Marcel! I really wish this was something simpler for people to just add to a config file. Makes sense to bring this in though, and I'll add a note about it to the contributing guide (I think it might be confusing in the readme). Appreciate the research!