Skip to content

GitHub Actions (Part 1) - relying on Azure access when there are issues! #322

@Seeta-BA

Description

@Seeta-BA

2 things made the GitHub Actions (Part 1) painful and filling me with dread for what I might experience with part 2 :-

  1. Could not create a new azure account due to the "validate you are human" page - the single option to press and hold a button which did not work (in Edge, in Chrome with the latest browsers, whether in or out of a VPN). There was no alternative - which then also meant there was part of the exercise I couldn't do where Azure was relied upon. (raised separate feedback on this to Microsoft as it was unacceptable)
  2. Awkward time - in the middle of updating npm versions from 20 to 24 on runners though some of the actions used are out of date - good that there are appropriate warnings.

The 2 issues together made this feel unnecessarily long, painful and unfinished ( though did whatever I could outside of the Azure stuff ). I could have accepted the second issue alone as upgrades/updates are important and there was appropriate workarounds but not the first and both together just slowed me down even more!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions