GitHub PR Workflow Check: Talawa API app starts (Docker)

[palisadoes]

Describe the bug

The GitHub PR workflow does not check whether the Talawa API app can start in Docker

To Reproduce

Steps to reproduce the behavior:

1. Make a change to the repo that makes the Talawa API app fail to start in Docker
2. Trigger the workflow to run as part of a PR
3. The workflow passes

and as expected:

1. Make a change to the repo that makes the Talawa API app start in Docker
2. Trigger the workflow to run as part of a PR
3. The workflow passes

Expected behavior

Steps to reproduce the behavior:

1. Make a change to the repo that makes the Talawa API app fail to start in Docker
2. Trigger the workflow to run as part of a PR
3. The workflow fails

and as expected:

1. Make a change to the repo that makes the Talawa API app start in Docker
2. Trigger the workflow to run as part of a PR
3. The workflow passes

We now have a test data that can be loaded that resides in the repo. This should be used as part of the test.

Actual behavior

• The Talawa API app isn't started and tested in the PR workflow

Screenshots

• N/A

Additional details

1. It must verify starting with Docker
2. Use this issue for reference:
   1. CI/CD : Check for Starting a Server. #1343

Potential internship candidates

• Please read this if you are planning to apply for a Palisadoes Foundation internship Student Internship Programs talawa#359

[rahulrana701]

@palisadoes I would like to work on this issue

[Kunalpal216]

I would like to work on this issue. @rahulrana701 any updates from you ?

[rahulrana701]

@Kunalpal216 yeah I am working on it

[palisadoes]

During the week of November 11, 2024 we will start a code freeze on the develop branches in Talawa, Talawa Admin and Talawa-API.

We have completed a project to convert the Talawa-API backend to use PostgreSQL. Work will then begin with us merging code in the develop branches to a new develop-postrgres branch in each repository.

Planning activities for this will be managed in our #talawa-projects slack channel. A GitHub project will be created to track specially labeled issues. We completed a similar exercise last year using a similar methodology.

Starting November 12, California time no new PRs will be accepted against the develop branch. They must be applied to the develop-postrgres branch.

There are some GSoC project features that will need to be merged into develop. These will be the only exceptions.

This activity and the post GSoC 2024 start date was announced in our #general Slack channel last month as a pinned post.

[nilaygit-10721]

Hello @palisadoes, may I work on this issue?

[RajvardhanT7747]

Hello @palisadoes I am very excited to contribute to these issue , May I contribute for these issue ?

[Cioppolo14]

If the issue has already been assigned, please don't ask to be assigned. We want everyone to get a chance.

[RajvardhanT7747]

Sorry mam extremely sorry don't misunderstand I have not seen previous issue had been assigned sorry

…

On Tue, Nov 12, 2024, 7:41 PM Crystian I ***@***.***> wrote: If the issue has already been assigned, please don't ask to be assigned. We want everyone to get a chance. — Reply to this email directly, view it on GitHub <#2638 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BC5GNG3T5JQBL35WZGWFXWL2AIEC3AVCNFSM6AAAAABRC4HEE2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZQGY2DEMRUG4> . You are receiving this because you commented.Message ID: ***@***.***>

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.