Create database table for Articles

[github-actions[bot]]

Dependencies

This issue should be completed after the issue "Articles - Create personal dokku dev deployment"

Overview

This issue involves creating the database table and migration file for Articles.

For step-by-step instructions, please see these portions of the lab writeup:

• https://ucsb-cs156.github.io/f24/lab/team01.html#the-two-database-tables-in-the-starting-code
• https://ucsb-cs156.github.io/f24/lab/team01.html#your-task-add-crud-for-additional-database-tables
• https://ucsb-cs156.github.io/f24/lab/team01.html#adding-a-database-table

Acceptance Criteria:

• [x] There is an @Entity class called Articles.java
• [x] There is a @Repository class called ArticlesRepository.java
• [x] There is a database migration file called Articles.json
• [x] When you start up the repo on localhost, you can see the table using the H2 console (see the file docs/h2-database.md for instructions.)
• [x] When you deploy the app to Dokku, you can see the table using the dokku postgres:connect team01-db command (use \dt to list the tables) (See https://ucsb-cs156.github.io/topics/dokku/postgres_database.html#postgres-command-line for more info.)

What to do next

When you've met all of the acceptance criteria:

Make a PR: Do a PR for this branch, being sure to enter a reasonable title and description.

In the description, include the text "Closes #n" where n is the number of this issue.

Then ask for a team member to review your PR.

Finally: drag this issue from "In Progress" to "In Review".

Review Others' PRs: Next, see if there are any PRs that need to be code reviewed and merged. Unless you are the first person on your team to complete a PR, there likely is at least one. See:

• General Code Review Advice
• Performin Code Reviews on Github

Start your next issue : Then, find the issue for "Create `ArticlesController..." on the Kanban board in the ToDo column.

• Assign it to yourself
• Drag into "In Progress"
• Create a new branch, starting from the branch for the issue you just finished.
• Start on the new issue.