Changed licensing information because swearing bad mmk?

Conversation 0 Commits 1 Files Changed 8

astoriaFloyd commented

Owner

Please work.

astoriaFloyd changed title from ~~WIP: Changed licensing information because swearing bad mmk?~~ to Changed licensing information because swearing bad mmk?

astoriaFloyd merged commit 3d0cd0e3a7 into main 3 years ago

astoriaFloyd referenced this issue from a commit

Merge pull request 'Changed licensing information because swearing bad mmk?' (#5) from Anti-Swearing into main

astoriaFloyd deleted branch Anti-Swearing

The pull request has been merged as 3d0cd0e3a7.

You can also view command line instructions.

Step 1:

From your project repository, check out a new branch and test the changes.

git checkout -b Anti-Swearing main

git pull origin Anti-Swearing

Step 2:

Merge the changes and update on Forgejo.

git checkout main

git merge --no-ff Anti-Swearing

git push origin main

Sign in to join this conversation.

No reviewers

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Loading…

There is no content yet.

Labels Milestones

Changed licensing information because swearing bad mmk? #5

Step 1:

Step 2: