Skip to content

fix: Automate copyright year#1136

Merged
jobenjada merged 2 commits intoformbricks:mainfrom
aryabyte21:copyrights-year
Oct 14, 2023
Merged

fix: Automate copyright year#1136
jobenjada merged 2 commits intoformbricks:mainfrom
aryabyte21:copyrights-year

Conversation

@aryabyte21
Copy link
Copy Markdown
Contributor

@aryabyte21 aryabyte21 commented Oct 14, 2023 •
edited
Loading

…to change manually

What does this PR do?

This PR aims to remove the hardcoded year in copyrights section of the website and automate it to the current year so we need not make new prs to change the copyrights year every time.

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • Chore (refactoring code, technical debt, workflow improvements)
  • Enhancement (small improvements)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change adds a new database migration
  • This change requires a documentation update

How should this be tested?

  • Test A
  • Test B

Checklist

Required

  • Filled out the "How to test" section in this PR
  • Read How we Code at Formbricks
  • Self-reviewed my own code
  • Commented on my code in hard-to-understand bits
  • Ran pnpm build
  • Checked for warnings, there are none
  • Removed all console.logs
  • Merged the latest changes from main onto my branch with git pull origin main
  • My changes don't cause any responsiveness issues

Appreciated

  • If a UI change was made: Added a screen recording or screenshots to this PR
  • Updated the Formbricks Docs if changes were necessary

@vercel
Copy link
Copy Markdown

vercel bot commented Oct 14, 2023

@aryabyte21 is attempting to deploy a commit to the formbricks Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Oct 14, 2023 •
edited
Loading

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title " fix: Automate copyright year". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

@aryabyte21 aryabyte21 changed the title the copyrights year will be fetched automatically every year no need … fix: the copyrights year will be fetched automatically every year no need … Oct 14, 2023
@aryabyte21 aryabyte21 changed the title fix: the copyrights year will be fetched automatically every year no need … fix(formbricks-com): automate copyright year. Oct 14, 2023
@jobenjada jobenjada changed the title fix(formbricks-com): automate copyright year. fix: Automate copyright year Oct 14, 2023
@jobenjada jobenjada enabled auto-merge October 14, 2023 16:45
@jobenjada jobenjada added this pull request to the merge queue Oct 14, 2023
Merged via the queue into formbricks:main with commit 5283741 Oct 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@aryabyte21 @jobenjada