<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Formerly The Pins Team</title>
    <description>The latest articles on DEV Community by Formerly The Pins Team (@thepinsteam).</description>
    <link>https://dev.to/thepinsteam</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Forganization%2Fprofile_image%2F1901%2F216dfd0d-e41f-4002-bf0d-eeaafa033934.jpg</url>
      <title>DEV Community: Formerly The Pins Team</title>
      <link>https://dev.to/thepinsteam</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/thepinsteam"/>
    <language>en</language>
    <item>
      <title>How do co-authors can sign commits, for vigilant-mode-enabled GitHub users?</title>
      <dc:creator>Andrei Jiroh Halili</dc:creator>
      <pubDate>Sat, 05 Jun 2021 14:03:08 +0000</pubDate>
      <link>https://dev.to/thepinsteam/how-do-co-authors-can-sign-commits-for-vigilant-mode-enabled-github-users-52h2</link>
      <guid>https://dev.to/thepinsteam/how-do-co-authors-can-sign-commits-for-vigilant-mode-enabled-github-users-52h2</guid>
      <description>&lt;p&gt;Since &lt;a href="http://stackoverflow.com/questions/1491001/ddg#1491022" rel="noopener noreferrer"&gt;re-writing commit histories&lt;/a&gt; that are been public is not &lt;a href="https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History" rel="noopener noreferrer"&gt;only discouraged by the Git Book itself&lt;/a&gt;, but also &lt;a href="https://blog.prototyp.digital/avoiding-the-messy-git-history/" rel="noopener noreferrer"&gt;disastrous for downstream (aka fork) maintainers&lt;/a&gt; and even can &lt;a href="https://medium.com/collaborne-engineering/git-branches-rewriting-history-and-avoiding-nightmares-part-1-b76f334f142c" rel="noopener noreferrer"&gt;be an nightmare&lt;/a&gt; since they need to rebase their work first, how do co-authors can safely sign their commits or do they need to do the &lt;strong&gt;chaos management&lt;/strong&gt; regarding that to ensure that it's &lt;code&gt;Verified&lt;/code&gt; not &lt;code&gt;Partially verified&lt;/code&gt; when someone visits their?&lt;/p&gt;

&lt;p&gt;This question assumes that at least one of the co-authors has Vigilant Mode enabled on their GitHub accounts and has at least one GPG key added into their account.&lt;/p&gt;

</description>
      <category>question</category>
      <category>github</category>
      <category>gpg</category>
      <category>help</category>
    </item>
    <item>
      <title>Team Updates — New Twitch channels and more (oh my!)</title>
      <dc:creator>Andrei Jiroh Halili</dc:creator>
      <pubDate>Tue, 18 Aug 2020 10:48:28 +0000</pubDate>
      <link>https://dev.to/thepinsteam/team-updates-new-twitch-channels-and-more-oh-my-bc6</link>
      <guid>https://dev.to/thepinsteam/team-updates-new-twitch-channels-and-more-oh-my-bc6</guid>
      <description>&lt;h3&gt;
  
  
  Team Updates — A new Medium publication, changed publication URL change, and Twitch channels? (oh my!)
&lt;/h3&gt;

&lt;p&gt;Since we rarely post updates about what we’re doing, many things are the things you missed even before the pandemic starts. Don’t worry, we got you covered!&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Heads up!&lt;/strong&gt; We updated this post on 9–1–2020 8:10PM (PH Standard Time) to fix some grammar and browoken link bugs.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h3&gt;
  
  
  🎊 A new publication for Recap Time
&lt;/h3&gt;

&lt;p&gt;Yes, you heard it. We got &lt;a href="https://medium.com/recap-time" rel="noopener noreferrer"&gt;a new, separate publication for Recap Time&lt;/a&gt;. Also, yours truly had made a new publication logo that used for Recap Time, here on Medium, and will be on &lt;a href="https://telegram.me/RecapTime" rel="noopener noreferrer"&gt;Telegram&lt;/a&gt;, &lt;a href="https://twitter.com/RecapTime" rel="noopener noreferrer"&gt;Twitter&lt;/a&gt; (and spoiler: &lt;a href="https://www.twitch.tv/recaptime" rel="noopener noreferrer"&gt;Twitch&lt;/a&gt;), soon.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F55z8jfkctc5bp46uvbow.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F55z8jfkctc5bp46uvbow.png" width="800" height="800"&gt;&lt;/a&gt;That was designed on Canva. Feel free to send us feedback so we can improve it.&lt;/p&gt;

&lt;p&gt;As we speak, we’re busy crafting the first issue that we'll release it on January 2021. But if you want a preview, be one of &lt;a href="https://pateron.com/ThePinsTeam" rel="noopener noreferrer"&gt;our patrons on Pateron&lt;/a&gt; to get exclusive access to our draft. Feel free to &lt;a href="https://medium.com/recap-time/newsletters/recap-time" rel="noopener noreferrer"&gt;subscribe to the newsletter&lt;/a&gt; to be the first to read the first issue once it’s out.&lt;/p&gt;

&lt;h3&gt;
  
  
  ℹ️ OwO, we changed our publication URL for the team blog.
&lt;/h3&gt;

&lt;p&gt;Months ago, we changed the publication name to The Pins Team Blog. On August 8, we asked Medium Support to change our publication URL into medium.com/thepinsteam-blog and they granted our wish, so we thanked them.&lt;/p&gt;

&lt;h3&gt;
  
  
  🔓We unlocked a special repository in our GitHub placeholder account.
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://github.com/ThePInsTeam/ThePinsTeam" rel="noopener noreferrer"&gt;Our special repository&lt;/a&gt; contains a list of team members and links where you can find us outside GitHub.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fwoz1sojihjcbij9wy77n.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fwoz1sojihjcbij9wy77n.png" width="655" height="248"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  ❔ And, Twitch?
&lt;/h3&gt;

&lt;p&gt;Yes, we got two Twitch channels. One for &lt;a href="https://twitch.tv/thepinsteam" rel="noopener noreferrer"&gt;the main channel&lt;/a&gt;, and &lt;a href="https://twitch.tv/recaptime" rel="noopener noreferrer"&gt;one for Recap Time&lt;/a&gt;. We’ll go live soon in the form of test broadcasts to learn how to broadcast. In a meanwhile, follow us there to be the first to get notified.&lt;/p&gt;

&lt;h3&gt;
  
  
  💬 Leaving Keybase when?
&lt;/h3&gt;

&lt;p&gt;&lt;a href="mailto:ryan@cyph.com?to=%22Ryan%20Lester%22%20%3Cryan@cyph.com%3E"&gt;Ryan Lester&lt;/a&gt; from Cyph sent us a message thru our &lt;a href="mailto:yourfriends@madebythepins.tk"&gt;yourfriends@madebythepins.tk&lt;/a&gt; address, inviting us to leave Keybase and look for alternatives. We’re not yet ready to move out, but we saved our special invite link for later use.&lt;/p&gt;

&lt;p&gt;And, that’s it for now. Follow us on &lt;a href="https://twitter.com/ThePinsTeam" rel="noopener noreferrer"&gt;Twitter&lt;/a&gt; and &lt;a href="https://t.me/UpdatesFromThePinsTeam" rel="noopener noreferrer"&gt;Telegram&lt;/a&gt; for more updates on what we do next. Have a nice day and stay safe!&lt;/p&gt;




</description>
      <category>recaptime</category>
      <category>staffblog</category>
      <category>teamupdates</category>
    </item>
    <item>
      <title>Handling requests to delete their account &amp; move to the @ghost account for self-hosted Dev.to instances</title>
      <dc:creator>Andrei Jiroh Halili</dc:creator>
      <pubDate>Sun, 31 May 2020 11:12:07 +0000</pubDate>
      <link>https://dev.to/thepinsteam/handling-requests-to-delete-their-account-move-to-the-ghost-account-for-self-hosted-dev-to-instances-5hd9</link>
      <guid>https://dev.to/thepinsteam/handling-requests-to-delete-their-account-move-to-the-ghost-account-for-self-hosted-dev-to-instances-5hd9</guid>
      <description>&lt;p&gt;I have a question on how the admins of &lt;a href="https://dev.to"&gt;Dev Commuity&lt;/a&gt; handle these types of account deletion requests. Is there any UI way in the Admin Dashboard to migrate stuff to &lt;a class="mentioned-user" href="https://dev.to/ghost"&gt;@ghost&lt;/a&gt; and nuke the account in question or should I need database access?&lt;/p&gt;

</description>
      <category>question</category>
      <category>help</category>
      <category>selfhosting</category>
    </item>
  </channel>
</rss>
