406CBC & 4077FC Photo Update, Add C2B55D

[Phaeton]

Describe your changes

406CBC & 4077FC Photo Update

Checklist before requesting a review

• I have performed a self-review of my code.
• While waiting for someone to review your request, please help review another open pull request to support the maintainers.

[github-actions]

Please only suggest/make any changes to the following files:

• plane-alert-db.csv: A list of interesting aircraft with tags, categories and links.
• plane-alert-pia.csv: A list that contains PIA planes.
• plane-alert-twitter-blocked.csv: A list of aircraft that will cause your Twitter account to be banned when used with docker-planefence. Please use it with care.
• plane-alert-ukraine.csv: A list with Ukrainian planes.
• plane_images.txt: A accompanying list that contains aircraft images.

All other files are generated from this file using the .github/workflows/create_db_derivatives.yaml GitHub action, and if you do not make your changes there, they will be overwritten and lost.

[rickstaa]

@Phaeton I checked your pull request, and it is correct. The check failed because you are working on your main branch, and the commit made by the https://github.com/sdr-enthusiasts/plane-alert-db/blob/main/.github/workflows/create_db_derivatives.yaml action does not re-trigger the https://github.com/sdr-enthusiasts/plane-alert-db/blob/main/.github/workflows/check_derivatives_change.yml action (see https://github.com/orgs/community/discussions/25702#discussioncomment-3248819). This can be fixed, but it will require a lot of code. I, therefore, think it is better to:

1. Fork the repo and create your branch from main.
2. Create a new feature branch (e.g. patch) to implement your changes.
3. Make your changes.
4. Issue that pulls requests from your feature branch!
5. Merge your feature branch into your own main branch, so you don't have to wait for the PR to be merged.

This is how GitHub recommends you create PRs to repositories. Does that work for you 🤔? I also updated the CONTRIBUTING.md file to represent this change.

[rickstaa]

@Phaeton I checked your pull request, and it is correct. The check failed because you are working on your main branch, and the commit made by the https://github.com/sdr-enthusiasts/plane-alert-db/blob/main/.github/workflows/create_db_derivatives.yaml action does not re-trigger the https://github.com/sdr-enthusiasts/plane-alert-db/blob/main/.github/workflows/check_derivatives_change.yml action (see https://github.com/orgs/community/discussions/25702#discussioncomment-3248819). This can be fixed, but it will require a lot of code. I, therefore, think it is better to:

1. Fork the repo and create your branch from main.
2. Create a new feature branch (e.g. patch) to implement your changes.
3. Make your changes.
4. Issue that pulls requests from your feature branch!
5. Merge your feature branch into your own main branch, so you don't have to wait for the PR to be merged.

This is how GitHub recommends you create PRs to repositories. Does that work for you 🤔? I also updated the CONTRIBUTING.md file to represent this change.

If you really want to work from the main branch, this is also possible, but then you have to run the create_db_derivatives.py file on your local machine to get the correct derivative files included in the PR.

[rickstaa]

@Phaeton I did some more tests, and it seems to work when the PR is created after the action has already committed the files (see https://github.com/sdr-enthusiasts/plane-alert-db/pulls). It fails when you create the pull request before the https://github.com/sdr-enthusiasts/plane-alert-db/blob/main/.github/workflows/create_db_derivatives.yaml has added the databases. I will update the CONTRIBUTING.md to reflect this.