Add Phoenix starter workflow

[jclem]

Add a Phoenix starter workflow

Phoenix is a popular web application framework for the Elixir programming language (for which we have a starter workflow). This pull request adds a workflow similar to the Elixir workflow—the main difference is that I've added a Postgres service (Postgres is the default database for new Phoenix projects).

Links

• Elixir
• Phoenix

To Do

• Get SVG and understand usage rights of Phoenix logo.

---

In the workflow and properties files:

• The workflow filename of CI workflows should be the name of the language or platform, in lower case. Special characters should be removed or replaced with words as appropriate (for example, "dotnet" instead of ".NET").
• The workflow filename of publishing workflows should be the name of the language or platform, in lower case, followed by "-publish".
• Includes a matching ci/properties/*.properties.json file.
• Use sentence case for the names of workflows and steps, for example "Run tests".
• The name of CI workflows should only be the name of the language or platform: for example "Go" (not "Go CI" or "Go Build")
• Include comments in the workflow for any parts that are not obvious or could use clarification.
• CI workflows should run on push to branches: [ master ] and pull_request to branches: [ master ].
• Packaging workflows should run on release with types: [ created ].

Some general notes:

• This workflow must only use actions that are produced by GitHub, in the actions organization, or
• This workflow must only use actions that are produced by the language or ecosystem that the workflow supports. These actions must be published to the GitHub Marketplace. Workflows using these actions must reference the action using the full 40 character hash of the action's commit instead of a tag. Additionally, workflows must include the following comment at the top of the workflow file:

  # This workflow uses actions that are not certified by GitHub.
  # They are provided by a third-party and are governed by
  # separate terms of service, privacy policy, and support
  # documentation.
  

• This workflow must not send data to any 3rd party service except for the purposes of installing dependencies.
• This workflow must not use a paid service or product.

[andymckay]

Looks good @jclem, we'll just need to get that logo 👍🏾

[bruce]

Looks good @jclem, we'll just need to get that logo 👍🏾

I reached out to @chrismccord to see if there's a process we need to follow.

[chrismccord]

This is great! GitHub has my permission to use the Phoenix logo for the starter workflows. I generally avoid making SVG publicly available as it becomes difficult to enforce usage with infinitely high res versions out there, so let me know if the following png is sufficient. Thanks!

[jclem]

Thank you @chrismccord and @bruce! I think the png is sufficient—I'll take a look Monday to double check.

[jclem]

@andymckay Do you know if a PNG will work for this? I noticed that iconName is just a string, so I'm curious if the rendering assumes that it will be an SVG.

[tonirmv]

#738

[github-actions]

This pull request has become stale and will be closed automatically within a period of time. Sorry about that.

[Monssif1]

مرحبا

[Monssif1]

انا جديد في هد الميدان