Update link to specifically point to the master branch. The badge itself is fine, as master is the base branch, and is where shields.io already points to
However, the link is a slightly different story as if you don't specify a branch, it shows all runs for the entire repo, which could be detrimental to new users, and possibly lead to non-standard or test installations, instead of the "release-ready" master build.
Replaced the retired badge w/sunset upstream badge, combined with updating the existing retired one to be changed back upon retirement as a courtesy to upstream until our rebrand is done.
There's still a lot of changes needed eventually to this to reroute things because it's going to be confusing going further into it and still seeing things linked to the old Atom branding for now when things might be better off in this repository. I at least made the wording changes Autumn suggested.
Since the upstream is sunsetting but it seems development is continuing here I thought it might be a good idea to update the readme to be more clear with the note at the top that it means the upstream Atom repo's and not the atom-community ones or whatever this may end up being called in the future.
Atom now has a script that checks for dependancy updates every time nighlty is pipeline is run.
The script mainly handles atom packages since the packages are not
deployed to npm
On top of this we also have dependabot setup to check and open prs
incase of updates.
Atom has recently moved to using Github Discussions as the main message
board for all Atom related stuff. It is important to have all Atom
related conversations on one platform to foster transparency.
